KNOSSOS performance issues

[fabiansvara]

This is a catch-all issue about knossos performance. With 10k nodes and M=5 on a high end desktop, continuous movement through the dataset sometimes feels like a slide-show. Performance is quite uneven, sometimes problems are less noticeable. Please help debug!

[Optiligence]

Slicing: While drilling you only dc and oc slice one vp (+arb?) and only tex offset the other 2 (since 4.1.1). When a cube boundary is reached, the other 2 have to be resliced too. Additionally new cubes are loaded and decompressed – in parallel – but this is not the performance issue, which arises because every time a dc or oc (distinguishment since 4.1.2) cube – which is visible (only master, directly after 4.1.2) – is finished, it requires an all-reslice. Movement: Doesn’t skip frames and is capped by slicing framerate, because it doesn’t retrospectively calc the time and the corresponding movement, but only moves one slice per event and events are blocked during reslicing. (side effect since february) Node rendering performance shouldn’t be an issue with 10k nodes.

[Optiligence]

Movement speed is now properly applied thru d07f2b96e6bea7858baa5ea9560ae03226d9cd7c.