http://bugs.winehq.org/show_bug.cgi?id=19889
--- Comment #29 from Alexey Loukianov mooroon2@mail.ru 2011-09-09 16:36:07 CDT --- Well, I've done the comparison between Steam client behaviour under Wine 1.2.3, 1.3.27 and 1.3.28. First of all this app seems to be laggish as hell in general, no matter which version of Wine I use. I suspect it to be mostly non-wine fault as I've got almost the same laggish Steam behaviour on my AMD C-50 based laptop with Windows 7 Starter 32bit. I think that something is overly wrong with the way Steam client is programmed as properly-written app shouldn't lag so much at drawing web pages and UI elements.
Besides that things definitely get worse with 1.3.27 and 1.3.28 comparing to the 1.2.3. Having chat window opened and maximized with 1.2.3 leads to no visible CPU utilization changes, system remains almost idle. As long as I force the UI to redraw something one of the CPU cores gets fully used and I can *feel* the lag it takes to draw Steam UI elements (like right-click popup menu, e.t.c.).
With 1.3.27 and 1.3.28 I've got constant 100% usage of one of the CPU cores as soon as I open chat window and maximize it (1680x1050 screen size). CPU usage keeps constant at 100% of one core as long as I've got text input area of the chat window focused (i.e. there's a cursor displayed there slowly blinking). As soon as I switch input focus to any other window, say main Steam client window or Firefox window opened on the second monitor (I've got TwinView setup here) - CPU usage drops to where it should be - i.e. into almost idle state.
There's no noticeable difference in behaviour between 1.3.27 and 1.3.28.
CPU usage spikes as the any Steam UI widgets interaction remains in place with 1.3.27/28 just like it was with 1.2.3. For example it is sufficient to hover the mouse over any web link displayed in any Steam client window to get the 100% usage of one of the CPU cores for about 1 second.