20,741
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 18:14, 30 December 2022
, 30 December 2022https://sourceforge.net/p/flightgear/mailman/message/37754850/
No edit summary |
m (https://sourceforge.net/p/flightgear/mailman/message/37754850/) |
||
| Line 7: | Line 7: | ||
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. | 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. | ||
Stuart spent a bit of time digging into the OSG DatabasePager as part of the WS3.0 work. It's all a bit complicated, and our behaviour has changed | |||
since 2020.3: | |||
The OSG_NUM_DATABASE_THREADS and OSG_NUM_HTTP_DATABASE_THREADS | |||
environmental can be used to set the number of threads used to load | |||
objects, scenery etc. The first is the total number of threads, and the | |||
latter is the subset of those threads that are used for HTTP. (I agree | |||
that's not at all obvious - see OSG osgDB/DatabasePager.cxx line 1209).That said, neither of the variables are relevant on next because FG | |||
explicitly sets the number of threads in fg_init (I haven't checked | |||
2020.3). I recently added code to next to support using | |||
/sim/rendering/database-pager/threads to set the number of threads. Note | |||
that this is again the total threads, and one of those will we still set up | |||
a single HTTP thread. I suspect we should simply set the number of HTTP | |||
threads to 0, as we don't use them.<ref>https://sourceforge.net/p/flightgear/mailman/message/37754850/</ref> | |||
{{Main article|CompositeViewer_support#DatabasePager}} | {{Main article|CompositeViewer_support#DatabasePager}} | ||