stuart wrote in Sun May 24, 2020 8:11 pm:On my system I think the problem is the random objects. With them enabled there are 6000+ drawables in view and 30-40fps. Disabling them I get 60fps, and the number of drawables drops to 650. Could you try that and let me know if it improves things for you?
This was taken from the osg stats, right ?
How complicated would it be to make these metrics available in the form of properties (on demand) ?
I think it's a standard osg visitor that is used to gather such metrics, right ?
The point being, we could then use Nasal to toggle samping on/off, and also gather stats for different combinations of locations/aircraft and draw masks - i.e. would have the basic building blocks to build a simple benchmark using Nasal, just by replaying an
fgtape file and toggling settings on/off while watching metrics like frame rate/spacing and number of drawable.
CPU vs GPU Bound (split from other topic)Hooray wrote:What's really needed is a benchmark suite - because different people have different hardware/systems, and are using different startup/runtime settings.
Thus, to make conclusive drawings, different combinations of settings must be tested, with performance being sampled in the background.
It would actually be a neat little project to create different rendering profiles (say different , save those to an XML and then replay a few
fgtape files while sampling performance metrics (frame rate, frame spacing) - this could be done with different draw masks set to enable/disable terrain/scenery
Something like this would be easy to create via Nasal, and the sampled data could be written to a CSV file for plotting purposes (think gnuplot).
Alternatively, we could also create a dedicated "Benchmark" add-on and use the Canvas system for plotting.
http://wiki.flightgear.org/How_to_manip ... s_elementsAll the building blocks are already in place:
http://wiki.flightgear.org/Graphics_card_profileshttp://wiki.flightgear.org/Flight_RecorderThus, the first step would be to copy the flight recorder dialog and remove unnecessary stuff, and then add a combo to load rendering settings from an XML file.
We could then grow a library of such benchmarks for different parts of flightgear (aircraft, scenery)
For plotting purposes, we can either write all sampled data to a file in $FG_HOME or show results via the Canvas