QbigBall

The information on how to change the logging level should be included in the README file of the linux version of the viewer. In many boards around the net you can find people complaining that the linux viewer is laggy, stuttery and extremely slow - and the reason is nothing else but that high default level of logging. Writing up to hundreds of lines a second to the logfile and pushing it through stdio dramatically slows down the viewer. In my case, just reducing the log level from INFO to ERROR and nulling the stdio-output increased the viewer's performance by at least factor three. Obiously there is a bug in the viewer's code concerning process threading. For testing purposes I turned it back to INFO and hat a closer look at it. Every time a logline is pushed, the graphics engine has a little lag, which adds up to a tremendous slowdown. Instead of multithreading, the main engine obivously waits for the log about what it just did to be output before continuing its process - a thing that must not happen in an engine meant to produce realtime graphics. Without the logging the engine speeds up like hell. Maybe it's a bug in the sources, maybe something went wrong, when Linden built the binaries - in any case LL should chance that preset value in the linux distribution of the viewer to ERROR by default.

Thanks Cerise! That was exactly what I was looking for. God - why the heck did they set such a high default level?! Just reduced it to ERROR and tested - this significantly reduces the viewers CPU load.

Hi folks, I'm new to SL, but after upgrading nvidias drivers and a little fiddling with the Open-GL config LL's viewer for linux is running quite smoothly on my System. There's just one drawback. This viewer is extremely verbose, throwing out hundreds and thousands of lines of no real interest, when started from command line, which is significantly reducing its performance, cause the system has to keep track of all that messages flooding the bash. Of course, easiest solution is to ground that output to /dev/null or launch it directly from the WM (which is pretty much the same), which increases the viewers performance, but then you get no information, in case something really important goes wrong. Is there a way to tell the viewer to only output information about critical errors instead of every this and that it's just connected to, opened, displayed and so on? Regards!