Difference between revisions of "Howto:Using additional OSG Pager Threads"

From FlightGear wiki
Jump to: navigation, search
m (https://forum.flightgear.org/viewtopic.php?f=17&t=38094&p=374606&hilit=pager+threads#p374612)
m (https://forum.flightgear.org/viewtopic.php?f=17&t=38094&hilit=pager+threads&start=15#p374620)
Line 3: Line 3:
 
you can configure OSG to use additional pager threads, which basically means the terrain cache gets additional CPUs it can use.
 
you can configure OSG to use additional pager threads, which basically means the terrain cache gets additional CPUs it can use.
 
see the OSG docs, it's just an environment variable, i.e. something like OSG_NUM_DATABASE_THREADS
 
see the OSG docs, it's just an environment variable, i.e. something like OSG_NUM_DATABASE_THREADS
 +
 +
Note that according to findings shared by Richard, when testing the database pager extensively (running with 20 DB pager threads), the main problem is the way that random objects (buildings, vegetation) are inserted into the scene graph doesn't seem to be compatible with lots of pager threads<ref>https://forum.flightgear.org/viewtopic.php?f=17&t=38094&hilit=pager+threads&start=15#p374620</ref>

Revision as of 03:35, 7 October 2020

This article is a stub. You can help the wiki by expanding it.

you can configure OSG to use additional pager threads, which basically means the terrain cache gets additional CPUs it can use. see the OSG docs, it's just an environment variable, i.e. something like OSG_NUM_DATABASE_THREADS

Note that according to findings shared by Richard, when testing the database pager extensively (running with 20 DB pager threads), the main problem is the way that random objects (buildings, vegetation) are inserted into the scene graph doesn't seem to be compatible with lots of pager threads[1]
  1. https://forum.flightgear.org/viewtopic.php?f=17&t=38094&hilit=pager+threads&start=15#p374620