Now that Wine has matured to the point of running many applications correctly, people are expecting them to run as fast as on Windows. Sadly, this is not always the case. Here are a few notes related to tracking down performance issues.

Wine C 2b 2b Runtime Library Error Pcsx2 Macbook
Wine C%2b%2b Runtime Library Error Pcsx2 Mac
Wine C 2b 2b Runtime Library Error Pcsx2 Mac Os
Wine C 2b 2b Runtime Library Error Pcsx2 Macbook Pro

Unzip the file provided, and copy or move the folder 'pcsx2-v1.5.0-dev-512-g7f3f6e9-windows-x86' to the location of your 'drivec/Program Files' folder. This is usually in homeWine Files, but if it's not, you'll have to track down your prefix. I had to do this by using the file explorer option in the wine.
After installing Fedora Media Writer and attempting to launch it on Windows 7 SP1 Professional 64-bit, I immediately get a crash dialog box titled 'Microsoft Visual C Runtime Library' that states 'This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.'

User Tips

Surprising as it may be, there really isn't a magic toggle to make everything faster. Anyway, for games, you can experiment with the following short list of settings:

if the game has an OpenGL mode, you could try using that. Notice that sometimes it enables code paths that aren't well tested (or are plain broken) in the game

otherwise

Link: miss to Comment, Like, Subscribe!

enable CSMT (https://wiki.winehq.org/Useful_Registry_Keys)
if you run your game from the command line, run it with WINEDEBUG=-all. That disables a bunch of error checking and validation
enable threaded optimization in the GL drivers: you can do that with environment variables, that's mesa_glthread=true for Mesa drivers or __GL_THREADED_OPTIMIZATIONS=1 for Nvidia proprietary drivers
disabling UseGLSL might slightly improve Direct3D performance and reduce shader compilation stuttering (but that has a chance to work only for d3d9 or older games and usually only with the Nvidia proprietary driver)
anything listed in the appdb as helping your particular game. For instance, http://appdb.winehq.org/objectManager.php?sClass=version&iId=19065 says Batman Arkham Asylum runs a lot faster if you set AmbientOcclusion=False in UserEngine.ini.
anything listed on the web as speeding up the Windows version. (For instance, http://www.hardocp.com/article/2009/10/19/batman_arkham_asylum_physx_gameplay_review/3 suggests Batman Arkman Asylum runs a lot faster if you set MotionBlur=False in that same file.)

The rest of this document is meant for developers more than users.

Related Discussion

Performance-related bugs

Here are some performance-related bugzilla queries:

Known Bottlenecks

applications that frequently compile D3D shaders may suffer from stuttering; see e.g. http://bugs.winehq.org/show_bug.cgi?id=23832 ('winetricks glsl-disable' helps some games with this, as it translates D3D bytecode into the lower level ARB_{vertex|fragment}_program language rather than GLSL and the driver is generally quicker at compiling those. Only works on Nvidia, though.)
applications that rely on precise thread scheduling will be disappointed (see e.g. http://hisouten.koumakan.jp/wiki/Linux_support#Resolved_bugs )
applications that use kernel events heavily may run slowly (e.g. Unreal Tournament 3 - Stefan?)
applications that are picky about what core a thread runs on may be disappointed (see e.g. http://bugs.winehq.org/show_bug.cgi?id=19748 )
some applications don't interact well with power management and supposedly get 30% to 80% higher frame rate if you run at full power unconditionally (see http://bugs.winehq.org/show_bug.cgi?id=24558)

Kernel?

The linux kernel might have something to do with performance. CONFIG_NO_HZ might make a difference, for instance.Here are a few notes on the subject:

World of Warcraft supposedly had pauses every 15 seconds unless you modify /etc/sysctl to change kernel.sched_batch_wakeup_granularity_ns and a couple other parameters (see http://wiki.archlinux.org/index.php/World_of_Warcraft#Kernel_Timing_Bug)
http://forums.gentoo.org/viewtopic-t-789725.html is a thread about kernel configuration and Doom3/Quake4/Prey performance.
http://code.google.com/p/realtimeconfigquickscan/ (you have to check the whole tree out) is a little script to check whether your system is set up for low latency (mostly for audio)

Measuring Performance

If you're making a tweak that speeds up one application, you probably want to run a bunch of different performance benchmarks before and after, to make sure it doesn't slow other applications down.

Many benchmarks exist for Windows. ['yagmark'] is a shell script that knows how to download and run several of them.3DMark 06 in particular is a classic benchmark we'd like to do better on.

Looking for Bottlenecks

There are many profiling tools that can help find bottlenecks in Wine.

Here are a few that have been used with some success:

oprofile (classic sampling whole-system profiler for linux, can profile into kernel, too)
sysprof newer, easier sampling whole-system profiler for linux

There are also a few graphic debug tools that might come in handy, like apitrace or renderdoc.

It's possible to build wined3d for Windows; this is cool because it might let you figure out if the bottleneck is in wined3d itself.

Game Performance Debugging Tutorial

First, the bad news: Often there is not a magic bullet to improve performance. It needs careful debugging and may be tricky to fix.

Copper pos registration code generator. Note that 'unlikely' below doesn't mean 'impossible', neither does 'likely' mean 'always'. Rules of thumb can be wrong, so some intuition, double-checking of assumptions and deviations from the guide are necessary.

1) Basic steps for debugging Direct3D performance problems:

Before digging too deep check a few common issues:

Keep your software up to date
Make sure you actually have a problem: Test the game on Windows on the same hardware. If it runs at the same speed there's probably nothing Wine can do to fix it. You're free to try though.
Make sure your System is OK. No background processes consuming CPU time, etc. Try disabling Desktop compositing
Check for log messages. Sometimes Wine knows it hits a slow path and writes a FIXME or WARN. Don't fix too much on such warnings, they may indicate a comparatively minor problem.
Watch out for high wineserver CPU usage
Currently 80% of Windows performance is a high water mark, few games run faster. Many games run around 50%, which means there's a lot of room for improvement. If your game runs even slower there are probably some nasty bugs around.

Some words about CSMT. The basic idea is to segregate wined3d's GL calls to a separate thread: wined3d functions indirectly called by the application threads queue messages to the command stream thread which, on its part, essentially keeps checking the queue and executing whatever instruction it finds there.
CSMT has been initially developed as a way to enhance wined3d performance, with the 'theory' being that by splitting the potentially expensive GL calls out of the application thread we can quickly return to the application code and hopefully lessen our CPU-side woes. That turned out to work pretty well but with a caveat: some commands (e.g. mapping buffers) actually NEED to wait for the operation to complete since they have to return data to the application. Without some 'tricks' when we get one of those commands we have to effectively wait until all the commands queued before it complete their execution, which means that the application thread has to block and wait, potentially throwing a lot of the performance improvement out of the window.
The version of CSMT initially introduced in 'official' Wine does without some of those tricks (specifically, those that weren't generally safe) and has some room for further performanc

Wine C%2b%2b Runtime Library Error Pcsx2 Mac