Support Board
Date/Time: Mon, 25 Nov 2024 07:48:48 +0000
Post From: Win 10 performance problem identified, with fix
| [2019-07-28 14:24:20] |
| User735389 - Posts: 189 |
|
I've been painfully stuck on Win 7 these past couple of years because I kept running into major performance issues when using Win 10 (in the order of 2-3x slower). Glad to say I've FINALLY figured out the issue. I didn't see this anywhere in the Help or forum but I figured this might help some of you out there as I've heard similar complaints of mysterious performance issues between 7 and 10. The new support for Open GL and its performance improvements got me thinking that Win 10 might have introduced some rendering penalties as it added new features. I noticed if you have multiple monitors with different scaling/dpi settings, windows can look really blurry when moving windows between screens. If you have 50 charts and Windows has apply scaling on every chart on every tick, that's gonna incur some penalty. Turns out that was the right path to follow. So.... If you are running multiple monitors, make sure all your monitors are set to the same scaling %. This wasn't a problem in W7 because you couldn't independently set the scaling for each monitor. Nice feature, poor implementation. I'll have to do more testing to make there arent any other performance problems when the market is live, but performance seems to be pretty even so far. Might be a bit painful for those of you running 4k laptops, but i've gotten use to 125% scaling on mines. Open GL likely won't solve this issue, but its performance enhancements will be welcomed none the less. Can't wait, it should bring me down to under 0.5 sec per tick. Edit: I also have a number of detached windows on my secondary monitors. I'm guessing they're inter-related. Not sure if this problem occurs if you run everything within the Main SC window, or if you run multiple instances on different monitors. Edit2: Another oddity. Win 10 shows 1 core being maxed out at 100%, Win 7 does not. I'm logging the time it takes for a study to do a round trip, and it's about the same between the two OSs. Quite odd, could be win 10 reporting cpu usage differently. So if you're testing this on your system, be aware. Edit3: You maybe able to resolve this, with differing monitors at different scaling options, by changing how Windows handles DPI settings per app. Right click the sierrachart_64.exe, properties. "Compatibility" tab. Click "Change high DPI settings". Check "Use this setting to fix scaling problems for this program instead of the one in Settings". Check "Override high DPI scaling behavior." Select "Application". Microsoft seems to be messing with this alot so play with these dpi/scaling settings until you get it working well for you. Last Edit: Wasn't able to get performance even to Win7, about 30-50% slower performance on win10 on average per cycle, with win7 a bit more consistent. Still, significant performance increase from before, and probably not noticeable to most people. i run 28 chartbooks, with 8 charts each in chartbook + 1 detached window each (on a 2nd monitor) + and addtional 8 detached charts (on a 3rd monitor). Wasn't able to test open gl, maybe it was too many charts but it would get stuck while loading historical data. Hopes this helps someone out there. Date Time Of Last Edit: 2019-07-31 10:43:35
|