1,746
edits
Howto:Using additional OSG Pager Threads: Difference between revisions
Jump to navigation
Jump to search
m
Howto:Using additional OSG Pager Threads (view source)
Revision as of 13:44, 26 May 2021
, 26 May 2021add categories, cleanup
m (add categories, cleanup) |
|||
| Line 1: | Line 1: | ||
{{Stub}} | {{Stub}} | ||
You can speed up scenery loading times by configuring OSG to use additional pager threads, which basically means the terrain cache gets additional CPUs it can use. | |||
See the OSG docs. To use additional threads just configure the following [[Environment variables|environment variable]] setting: <code>OSG_NUM_DATABASE_THREADS</code>. For a 4 core system try setting this to 2 or 3. For a 6-8 core CPU try increasing to 5-8. Try reloading scenery via the debug menu to see benefits. | |||
This has the potential to speed up loading of scenery like OSM2City. People on the forum have reported instability. This will ''not increase FPS'', merely improve loading times - which will only be visible in areas with a lot of scenery objects. | |||
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> | 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> | ||
<references /> | |||
[[Category:Multicore]] | |||
[[Category:Environment variables]] | |||