However, it seams to be using allot of processor power, i'm seeing spikes of up to 70% with an average of around 30%, this is on
a 3GHZ processor,
There are a lot of factors in processor consumption. Your hardware and settings will change things drastically. The biggest CPU factor should be pretty obvious, all the graphics. In Tuning of power consumption, naturally I use MegaTune as a baseline and target keeping CPU consumption even. But these factors will drive that up:
- Large screen - If the dash is large it takes more power to paint
- AntiAliasing On - depending on how well your hardware supports this it will quickly double your CPU usage. MegaTune never uses anti-aliasing
- Data Rate - If you turn that to 25 fps or max, that can create a lot more screen paints.
- Which Dash you are using - Different dashboards have a different number of Gauges, some gauge styles take more CPU. Like the Analog Bar, that still has some optimizing opportunities, and uses more CPU than most of the others.
Another place TSMS uses more CPU is when the dialogs are open with like the 3D tables, because the Dash keeps going Where in MegaTune it stalls.
So is it Java, no. As on even settings, TS uses less CPU power than MegaTune, but the extra bells and whistles start asking for CPU. You can't imagine the time spent measuring nano seconds of paint times
. If you have a Gauge that takes 5 millisecond to paint, that sounds Ok, no way.
5ms X 12 gauges X 20 fps = 1200 or 1.2 seconds of work every second, in other words the CPU is pegged.
Try switching to the Default dash and turning Anti-Aliasing off and data rate set to 15-20. That puts TSMS on an even playing field with MegaTune and you will find CPU usage on par or lower than MegaTune.
Now in a case like yours where you have the CPU to use, I go ahead and use it when needed. But it is throttled for slower machines. So you can still run on an 800 MHz laptop and should never see the processor pegged, but the frame rate may slow when needed to keep the app responsive.
