Murat Yilmaz

Isn't the Swift random API seedable, like `UInt64.random(in:)`

I need to check if it will resolve the issue. But back to the original question is there a reason why we are holding the dictionary with all the values...

Sounds great! Maybe it would also be possible to just limit the processing part by measuring the time spend forcing it to not drop the target frame rate. Like maintaining...

Yes exactly, not sure if it will be a reliable solution but could be a simple one instead of going multi-threaded and also depending too much on the rendering part.

I've just tested v2 again with a 1gb text file, the numbers look good now. Having vsync on is now twice as fast, is the default path doing anything different...

Yes with throttling turned off we reach the same numbers as with vsync on! It is interesting for me to see running the same test with splat2 is climbing up...

Should also solve #10