Investigate HDF5 file performance

[ManuelHu]

Not urgent and probably not necessary, but

• check that Geant4 HDF5 writing parameters are best for performance in our use case(s)
• check if we can change/influence them?

[tdixon97]

It might also be worth checking the memory usage, I find some steps use alot of memory (maybe lh5 converting), which can cause issues...

[ManuelHu]

I will do a test. LH5 converting is actually a two-step-process (dry-run + actual convert).The dry-run runs on a (I think memory-mapped+COW, hopefully?) in-memory copy of the file, that might be expensive...

[ManuelHu]

with #138, the memory overhead should hopefully be gone

[ManuelHu]

The only parameter that we could reasonably change is the deflate (?) compression level 1-9, default 1.

the toolx::hdf5 also has some options for chunking, but they are not accesible via the analysis manager interface.