Author |
Message |
Zauber Exonar
Joined: 2009-09-08 01:27:46 Posts: 172
|
Under the current version of Cool VL Viewer, any time I reduce or disable a particular deferred rendering feature (in particular, RenderDeferredGI, RenderShadowDetail, RenderShadowResolution) the viewer's framerate drops to the single digits. In order to fix it, I need to turn deferred rendering off and then back on. I didn't start experiencing this until I updated to 1.26.2 (6), while previously I was using 1.26.2 (4).
|
2011-11-22 08:55:08 |
|
 |
Zauber Exonar
Joined: 2009-09-08 01:27:46 Posts: 172
|
Correction: changing the deferred rendering debug settings period causes the heavy lag until I turn deferred rendering off and then back on.
|
2011-11-22 08:56:55 |
|
 |
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 6043
|
Please, read the rules of this forum and report all required info. In particular, I need the SecondLife.log file. Note however that there is no change that occurred between v1.26.2.4 and v1.26.2.6 that could even remotely explain a change in rendering performances and that I cannot reproduce your issue here (although I got the same graphics card and driver), so the issue is probably in something you changed in your system... One thing intrigues me though: your processor reports as running at only 800MHz... with the viewer running, it should be at full speed (3.2GHz)... Probably is your system not properly detecting the processor load: try forcing the CPUFreq governor to "performance" or (for a desktop computer where power consumption doesn't really matter), recompile your kernel with frequency scaling disabled and disable frequency scaling in your BIOS as well.
|
2011-11-22 09:33:47 |
|
 |
Zauber Exonar
Joined: 2009-09-08 01:27:46 Posts: 172
|
Well, after turning off the x4 anti-aliasing, the bug stopped occurring, but did not reproduce after I turned the anti-aliasing back on. If I see it happening again, I'll grab a log file and post it.
Also, the Phenom II CPU's are able to underclock the cores at different values independently, so while running the viewer with the ondemand governor, one core tends to run full speed while the others don't. I think that might have confused the viewer, causing it to detect that the CPU was running at 800mhz instead of the full speed of 3500mhz on the core it was running on.
|
2011-11-22 10:04:24 |
|
 |
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 6043
|
Frankly, your issue does seem related to a bad CPU load detection leading the speed governor to adopt a bad frequency... I always hated those stupid speed stepping features anyway (when I buy a fast CPU, it's not to see it lazying during half a second at low speed till the governor finally decides that it could switch it at full speed and does so just half a second before the process that lead to load the processor finishes what it had to do...). I keep these *off* (and more exactly, not compiled in the kernel), on *all* my systems, including on laptops !
|
2011-11-22 11:24:40 |
|
 |
Zauber Exonar
Joined: 2009-09-08 01:27:46 Posts: 172
|
Doesn't appear to be the case. Just now I tested with both the Ondemand and Performance governors and didn't see the problem reproduce. I also tested the powersave governor to underclock all cores to 800mhz, and I was still getting better performance than when I had the severe lag, which was bad enough to lag the mouse cursor.
|
2011-11-22 11:45:48 |
|
 |
Zauber Exonar
Joined: 2009-09-08 01:27:46 Posts: 172
|
I encountered the problem again. It appears to have started after I turned on the Global Illumination option for deferred rendering, but this time it persisted even after turning Deferred rendering off and back on.
I've supplied the log file, but had to compress it because it was around 10x larger than the maximum file upload size.
|
2011-11-22 13:04:45 |
|
 |
Henri Beauchamp
Joined: 2009-03-17 18:42:51 Posts: 6043
|
Your lag seems due to another cause...
There are loads of "WARNING: constrainVolumeParams: LLVolumeMessage::constrainVolumeParams() - forced to constrain incoming volume params: 0x00NN" log lines (sometimes issued a dozen of times a second).
My guess is that some object in the place where your avatar rezzed contains objects with out of range parameters (non-standard limits such as 99% holes and such in prims). The lag is probably the result of the log spamming with the warnings.
I added an anti-spam measure for next release.
|
2011-11-23 00:01:24 |
|
 |
Zauber Exonar
Joined: 2009-09-08 01:27:46 Posts: 172
|
Not sure it was 99% holes or anything. I do have those on my region at InWorldz, but I was also seeing this bug occur at the region Paradise Landing in Second Life.
|
2011-11-23 08:15:36 |
|
|