Canvas SVG: Difference between revisions

Line 2: Line 2:


== Background ==
== Background ==
With MFDs making heavy use of SVG files, our way of using a custom scripted parser implemented in Nasal (svg.nas) is adding up considerably. i.e. performance is severely affected when processing such files.
Some lower end RPi/Intel based computers are taking ~15 seconds to show the FG1000 device.
 
So there's currently a discussion taking place to optimize/port or re-implement Canvas SVG handling - could some more people please report here how long initialization of the FG1000 is taking for them ? Ideally, by using just the debug menu and checking how much time it takes for the PDF to show up ?
 
With some new MFDs making heavy use of SVG files, our way of using a custom scripted parser implemented in Nasal (svg.nas) is adding up considerably. i.e. performance is severely affected when processing such files.


On some platforms, just the initialization of the [[FG1000]] is taking ~15 seconds - profiling shows most of the time is spent in ~1500 context switches between Nasal and C++ respectively.
On some platforms, just the initialization of the [[FG1000]] is taking ~15 seconds - profiling shows most of the time is spent in ~1500 context switches between Nasal and C++ respectively.


== Ideas ==
== Ideas ==