CPU load in VR?

[Globusdiablo]

I thought I had plenty of headroom on my i5 6600k clocked at 4.2 Ghz, until someone asked me to actually take a reading. So I installed HWiNFO64 only to find that my CPU is running 90 to 100% load with following settings and in the following environment. I bumped my CPU to 4.6 with a small perceived gain of maybe 5% headroom.

Would other VR users please share what kind of CPU loads they have with the following settings?:

Environment:

• Parked in a station (not below deck)
• 90 FPS (hit ctrl + F on your keyboard)
• Ship facing the exit

Settings:

• SS: 0.65
• HMD-Q: 2.0
• Draw Distance: Max
• AA: Off

The rest of the settings are less important I think, so no need to set everything to the exact same.

This is only meant as a general comparison, as some have said loads as low as 25% on their CPUs during load with Vive/Oculus. Which of course makes me very jealous.

Edit for clarity: I use a Vive.

 

[mindfaQ]

I'm at 80 - 90% in stations, but with SS 1.0 and HMD 1.0 and less draw distance. CPU is a i5 6600k @4.1 Ghz, also Vive. So your values seem plausible.

 

[bitstorm]

CPU1: ~65%
CPU2: ~40%
CPU3: ~45%
CPU4: ~30%
CPU5: ~30%
CPU6: ~30%
CPU7: ~30%
CPU8: ~30%

i7 6700k

 

[Globusdiablo]

Thanks guys. Good to know my system isn't borked. I'm a bit envious of bitstorm though.

 

[bitstorm]

Actually is 90-100 a bit odd?

I mean the 6600 and 6700 are the same really aren't they, mine has a few more cores but I'm not sure ED is using them anyway?

 

[Globusdiablo]

Actually is 90-100 a bit odd?

I mean the 6600 and 6700 are the same really aren't they, mine has a few more cores but I'm not sure ED is using them anyway?

I don't think so. Load dives to 50s and 60s as soon as I leave the station for some reason. Did you do your measurements with the settings/environment I suggested?

 

[TorTorden_VR]

I have noticed this myself.

Hence this thread.
https://forums.frontier.co.uk/showthread.php/332676-lt-45fps-in-Resource-sites

Basically my 980ti seem to running around 50%, and my cpu 30% higher.

Sometimes things get hectic enough in combat to actually not even maintain spacewarp framerates. And it becomes a total garbled mess.

So I almost bought a ryzen build, canceled that, almost bought a kaby lake build but never actuated it.
But have ordered a price reduced i7-4790K, hope to have it, and install it within the week and can run some comparisons.
Honestly half the reason to get this is to test the difference between just my i5 4670k and this.
It's a reasonable jump though, more cache, more threads, more speed.

 

[erbse-1]

CPU1: ~65%
CPU2: ~40%
CPU3: ~45%
CPU4: ~30%
CPU5: ~30%
CPU6: ~30%
CPU7: ~30%
CPU8: ~30%

i7 6700k

elite or windows is spreading usage to your virtual cores too but is using only 4 physical cores. If your pysical core have 100% load and the HT-core 0% it will spread to 50% c1 and 50% to virtual c2.

@globusdiablo
nice finding. Same here with a i5 3570k @ 4.8GHZ/R9 290 @ 1200mhz and a DK2-clon (deepoon e2): in stations facing to exit up to 80% cpu load ("measured" with task manager in win10).

Settings:
SS: 1.0
HMD: 1.25
shadows mid
blurr off
hbao off
all other maxed out

 

[dape]

I was wondering as I had a very high CPU utilization. It seems to now have settled at around 65%. The readings of the Taskmanager are a bit misleading. I use Process Explorer. A very handy tool. https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx

Windows 10 home 64bit
i5 6600k 4.6Ghz
GTX 1080 OC
Asus Z170 pro gaming bios v. 3202
16G DDR4 2400

sitting outside Jaques station (that's where I got 90%+ CPU load in the past and also inside the station)

Cinebench R15

 

[Globusdiablo]

I was wondering as I had a very high CPU utilization. It seems to now have settled at around 65%. The readings of the Taskmanager are a bit misleading. I use Process Explorer. A very handy tool. https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx

Windows 10 home 64bit
i5 6600k 4.6Ghz
GTX 1080 OC
Asus Z170 pro gaming bios v. 3202
16G DDR4 2400

sitting outside Jaques station (that's where I got 90%+ CPU load in the past and also inside the station)

http://i.imgur.com/Itm5zJ1.png

http://i.imgur.com/7qRGekR.jpg

http://i.imgur.com/yghfMms.jpg

http://i.imgur.com/ianpNJB.jpg

Cinebench R15
http://i.imgur.com/qv9MrWK.jpg

Nice Informative write-up. Thanks.

 

[Globusdiablo]

http://i.imgur.com/7qRGekR.jpg

I see you haven't unlocked the your draw distance. What gives?

Monitored a bit more today, keeping an eye on my new 4.6 OC.

Using the bios tools of my Z170 pro gaming MB, I set CPU load-line calibration to level 5, and maxed CPU current capability at 140% (I think this ensure that I have the volts needed to drive the 4.6 Ghz, right?).

I kept HWiNFO64 running in the background during a two hour session, and ended up back at my initial testing ground/setting.

And here are my findings:

Voltage seems to stay reasonable at max loads (1.309 V). Max CPU load is "ok" I guess at 94.9%. Current CPU load (testing ground) is ok at 76.6%.

Thanks to the commanders for introducing me to the delights of CPU OC and monitoring.

Seeing as CPU load is "high" on a VR specific, high visual setting, maybe I should splash the extra cash when creating my next build (2 years from now) and get an i7?

 

[-VR- Max Factor]

I see you haven't unlocked the your draw distance. What gives?

Monitored a bit more today, keeping an eye on my new 4.6 OC.

Using the bios tools of my Z170 pro gaming MB, I set CPU load-line calibration to level 5, and maxed CPU current capability at 140% (I think this ensure that I have the volts needed to drive the 4.6 Ghz, right?).

I kept HWiNFO64 running in the background during a two hour session, and ended up back at my initial testing ground/setting.

And here are my findings:

http://i1262.photobucket.com/albums/ii604/globusdiablo/4.6_zps30qn0ysn.jpg

Voltage seems to stay reasonable at max loads (1.309 V). Max CPU load is "ok" I guess at 94.9%. Current CPU load (testing ground) is ok at 76.6%.

Thanks to the commanders for introducing me to the delights of CPU OC and monitoring.

Seeing as CPU load is "high" on a VR specific, high visual setting, maybe I should splash the extra cash when creating my next build (2 years from now) and get an i7?

I will be updating my system soonish. But will most likely go for an AMD 1600x, 6 cores, 12 threads.
I'm sure any issues will have been ironed out by the time I get it.

 

[dape]

I see you haven't unlocked the your draw distance. What gives?

Monitored a bit more today, keeping an eye on my new 4.6 OC.

Using the bios tools of my Z170 pro gaming MB, I set CPU load-line calibration to level 5, and maxed CPU current capability at 140% (I think this ensure that I have the volts needed to drive the 4.6 Ghz, right?).

I kept HWiNFO64 running in the background during a two hour session, and ended up back at my initial testing ground/setting.

And here are my findings:

http://i1262.photobucket.com/albums/ii604/globusdiablo/4.6_zps30qn0ysn.jpg

Voltage seems to stay reasonable at max loads (1.309 V). Max CPU load is "ok" I guess at 94.9%. Current CPU load (testing ground) is ok at 76.6%.

Thanks to the commanders for introducing me to the delights of CPU OC and monitoring.

Seeing as CPU load is "high" on a VR specific, high visual setting, maybe I should splash the extra cash when creating my next build (2 years from now) and get an i7?

settings, voltage and temps look perfect. dont know about the 140% though.

no need to upgrade anything soon. maybe some day when the 1080 gets replaced. no idea if the next gen processors will be supported on the Z170 mainbords.

 

[shadragon]

I don't think so. Load dives to 50s and 60s as soon as I leave the station for some reason. Did you do your measurements with the settings/environment I suggested?

When in the station you have to deal with a lot more graphical info than when in space. There's a lot of textures that need to be loaded, panels, struts, pads, other ships and paint jobs, etc. They are loaded by the CPU to the GPU from your HD.

You are also dealing with network information being sent to the servers and other CMDR's, if they are in your instance. So something like being inside a station on a CG with eight other CMDR's will tax your CPU heavily coordinating all that data.

 

[Globusdiablo]

Just tested CPU load in beta 4, and it's hairy.

Running at 4.6 Ghz, all cores are maxed at some point during a station to station flight. Temps are fine, but I don't want to push my CPU further than 4.6 Ghz.

Optimisation needed FD.

 

[TheChafing]

Just tested CPU load in beta 4, and it's hairy.

Running at 4.6 Ghz, all cores are maxed at some point during a station to station flight. Temps are fine, but I don't want to push my CPU further than 4.6 Ghz.

Optimisation needed FD.

http://i1262.photobucket.com/albums/ii604/globusdiablo/temp and load beta 4_zpswksovsq0.jpg

Interesting that you're actually maxing out a Skylake CPU. I've noticed some smearing of the HUD when turning the ship around for launch at surface ports that I always assumed was just an artifact of the way the hud is rendered, but the other day I noticed the background was also being smeared. I guess that's reprojection at work? Oddly, I never notice this going on while actually flying - it's just inside stations when the pad is turning around.

I'll have to try the same test this evening. I'm running a 5820K at 4.3 GHz and a GTX 1080 at 2100 MHz. Assuming the game isn't designed to use the two extra cores, your CPU should be a little faster than mine, and a cursory look at GPU-Z suggests that my graphics card is maxing out around 85% utilization.

The really frustrating thing is that there's hardly anything to upgrade to. A 7700K isn't that much faster unless you get one of the golden 5GHz capable ones.

 

[Globusdiablo]

...The really frustrating thing is that there's hardly anything to upgrade to. A 7700K isn't that much faster unless you get one of the golden 5GHz capable ones.

Indeed. General load seems appropriate, but a 6600K OCed to 4.6 Ghz without any thermal throttling shouldn't be choking. This is a consumer grade game after all.

 

[TheChafing]

What HMD do you have? I thought you had stated, but now I can't find it.

I'm using a Rift, which I understand imposes some extra CPU overhead, or at least is worse about that than the Vive. I'd be interested to see results of a setup that uses a Vive instead.

Either way, I only ever notice this at a point where the game isn't even interactive, so I guess I can live with it, but it still bugs me. [ugh]

 

[Globusdiablo]

What HMD do you have? I thought you had stated, but now I can't find it.

I'm using a Rift, which I understand imposes some extra CPU overhead, or at least is worse about that than the Vive. I'd be interested to see results of a setup that uses a Vive instead.

Either way, I only ever notice this at a point where the game isn't even interactive, so I guess I can live with it, but it still bugs me. [ugh]

Sorry. I updated my initial post for this info as well. I'm on the Vive.

Yeah, general load seems fine. Haven't been able to pinpoint the spike.

 

[TorTorden_VR]

Interesting that you're actually maxing out a Skylake CPU. I've noticed some smearing of the HUD when turning the ship around for launch at surface ports that I always assumed was just an artifact of the way the hud is rendered, but the other day I noticed the background was also being smeared. I guess that's reprojection at work? Oddly, I never notice this going on while actually flying - it's just inside stations when the pad is turning around.

I'll have to try the same test this evening. I'm running a 5820K at 4.3 GHz and a GTX 1080 at 2100 MHz. Assuming the game isn't designed to use the two extra cores, your CPU should be a little faster than mine, and a cursory look at GPU-Z suggests that my graphics card is maxing out around 85% utilization.

The really frustrating thing is that there's hardly anything to upgrade to. A 7700K isn't that much faster unless you get one of the golden 5GHz capable ones.

It happens whenever it throttles fps, its just really apparent in such an instance because there are something other than black space beyond the windows.
It's also very easy to see this in the srv when making turns or looking down past the wheels or floor.