Cool VL Viewer forum

View unanswered posts | View active topics It is currently 2021-04-13 10:42:03

Reply to topic  [ 5 posts ] 
High CPU 
Author Message

Joined: 2019-12-13 12:01:19
Posts: 8
Reply with quote
Not sure if this is a bug but for the last 3 updates i am having high cpu issues , i run coolvl at 6% cpu and when i tp or fly it goes up to 12%. but the last 3 updates are still running at 6% but when i tp or fly cpu goes up to 79% and gradually comes back down to 6%, so i have stayed on old viewer till i find out if this correct behaviour. i have compressed the log files but it says its too big to upload it?

Cool VL Viewer v1.28.2.14, 64 bits, Mar 13 2021 10:13:28
CPU: Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (3600 MHz)
Memory: 32688MB
OS version: Microsoft Windows 10 64 bits v10.0 (build 10586.867)
Memory manager: OS native
Graphics card vendor: NVIDIA Corporation
Graphics card: NVIDIA GeForce RTX 2060 SUPER/PCIe/SSE2
Windows graphics driver version: 27.21.0014.6589
OpenGL version: 4.6.0 NVIDIA 465.89
Detected VRAM: 8192MB
J2C decoder: OpenJPEG:
Audio driver: FMOD Studio v2.01.08
Networking backend: libcurl/7.47.0 OpenSSL/1.0.2l zlib/1.2.8
Embedded browser: CEF3 plugin v88.2.8+ge484012+chromium-88.0.4324.150

2021-04-04 06:49:32

Joined: 2011-09-17 11:12:19
Posts: 294
Reply with quote
The viewer will always use as much CPU as it can. If it goes high it could just mean that there has been performance improvements, perhaps with cache, since flying and tp'ing means things have to rez faster.

If high cpu is an issue for you, you can throttle it using YieldTime in the debug settings, with a computer like yours I don't expect you will notice much of an impact with a 5 or 10ms yield.

I think if you only attach the latest log file that will be enough, but Henri can correct me on this. That one should compress and fit fine in the memory

2021-04-04 08:11:17

Joined: 2019-12-13 12:01:19
Posts: 8
Reply with quote
thank you catten, just this is very new behaviour for me so wondered if it was a change in the way the viewer was compiled or it was my pc.

managed to get log files posted finally lol

log files [21.79 KiB]
Not downloaded yet
2021-04-04 08:18:26

Joined: 2009-03-17 18:42:51
Posts: 4559
Reply with quote
This is in no way a bug but the expected behaviour and the result of the new multi-threaded image decoder implementation, that allows to rez textures (much) faster.

The viewer simply makes the best use it can from your CPU by saturating its cores when it needs to decode textures.

If for whatever reason you do not want your CPU exploited in the best possible way, you still can manually configure the viewer to reduce the maximum number of cores in use during image decoding, or even to revert it to the older releases and other viewer's behaviour (mono-threaded image decoding), by changing the NumImageDecodeThreads debug setting (set it to 1 for mono-threaded, or any other number for more threads; the 0 default will let the viewer decide how many threads your CPU can run)...
There are also the "Duration of texture fetch boost after TP" setting (in "Preferences" floater, "Cool features" tab, "Miscellaneous" sub-tab) and the "Boost textures fetches with speed" (in the "Advanced" -> "Rendering" -> "Textures" menu) option/feature that you may want to disable if you prefer a cooler CPU at the cost of slower textures rezzing...

2021-04-04 08:33:55
Profile WWW

Joined: 2019-12-13 12:01:19
Posts: 8
Reply with quote
Thank you very much henry for explaining all that to me! will download the newest update with confidence!

2021-04-04 08:46:47
Display posts from previous:  Sort by  
Reply to topic   [ 5 posts ] 

Who is online

Users browsing this forum: No registered users and 1 guest

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group
Designed by ST Software.