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:47, 26 May 2021
, 26 May 2021no edit summary
m (add categories, cleanup) |
mNo edit summary |
||
| Line 3: | Line 3: | ||
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. | 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 | 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 or higher. For a 6-8 core CPU try increasing further to use extra cores. Try reloading scenery via the debug menu to see benefits - look at the CPU utilisation. | ||
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. | 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. | ||