Support for Single Writer Multiple Reader (SWMR)? about hdf5.node HOT 7 OPEN

Hi @KirmTwinty , thank for the example.

I'm working it in to the master branch now that v12 branch is merged. Probably will work in the swmr write as well and make it work from nodejs

from hdf5.node.

Good timing! I was about to ask the same...

from hdf5.node.

Hi,

http://hdf-ni.github.io/hdf5.node/ref/file.html File.prototype.enableSingleWriteMultiRead() is to turn it on. I don't have a good test case for it; we test and see if it works

from hdf5.node.

Apparently, it doesn't work, not implemented.

Since I needed it for a professional project,
I have made a fork of the v12 branch
in my repository, implementing an SWMR Reader only:

v12+SWMR branch @KirmTwinty

You need to change a bit your code though since the creation of a new object Dataset that behaves like a Group object was needed.
Check out the About this fork section in the readme.md

from hdf5.node.

Great news, thanks!
I actually applied the Group and File reading principles to Dataset.

The good thing is that the library will principally rely on the bare H5 library (which could be done for any reading and writing mode). The different calls to the H5LT one could be removed?

Do not hesitate if I can help.

from hdf5.node.

Hi @KirmTwinty, Thank you

The H5LT was the beginning; thought it would get the furtherest at the time. Internally h5_lt.hpp has been relying more and more on the bare h5. Tables, packet tables and image APIs will still need the lite(I don't have an energetic reason to rewrite those).

Mostly want to keep the javascript side steady for users with potential additions. The SWMR is probably the most useful new addition to users out there. The idea is not to replicate every API function of hdf5 but map the hierarchical nature of the data and attributes to the nature of js without the user needing to learn a c style API replication but get to their data/attributes the way js already is designed. Have to think some more.

from hdf5.node.

I totally understand! Thank you for coming with this.

My intend was to suggest a potential performance improvement, not to criticize :)

I see your point for trying to keep JS philosophy while interfacing with a C API, not such an easy task.

from hdf5.node.