Hi Kirk, A Tuesday 20 April 2010 17:56:53 Kirk Harrison escrigué: > Francesc, > > I do plan on using (or at least testing) the buffered file (H5FD_STDIO) for > the hard drive based portion of my long-term storage. I also have a > particular requirement to run in a disk-less environment for a much less > amount of (current) data than I plan to store on the disk. I plan to > periodically copying/moving the data from the memory file to the disk file > by developing a server application responsible for its management. > > I also have multiple clients which need access to the data and am planning > on mirroring the memory-based portion of the data on each client's > workstation with links to the network based disk storage (when available) > for data beyond the memory file's capacity. > > Performance has been an issue in the legacy implementation for getting the > data to the clients which is another reason I am experimenting with this > configuration. > > I guess an alternative architecture would be do determine at runtime if a > disk file was available and if not open a memory-based file and use it > exclusively, otherwise exclusively use the networked hard drive... which is > probably more in line with your suggestion. I plan to evaluate this as > well. > > Of course, I am open to easier and/or better implementation ideas. Thanks > for your input.
No problem. If you have special reasons, then go ahead and try the CORE driver. My experience was that, for reading, the performance was slightly worse than using a regular H5FD_SEC2 driver. I suppose the reason is that HDF5 has to duplicate the exiting data in file to memory, and that takes some time. But for writing (and without backing_store active, of course) you *might* get some speedup. -- Francesc Alted _______________________________________________ Hdf-forum is for HDF software users discussion. [email protected] http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org
