Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Storage Benchmarks #3

Open
kmpaul opened this issue Apr 2, 2019 · 4 comments
Open

Storage Benchmarks #3

kmpaul opened this issue Apr 2, 2019 · 4 comments

Comments

@kmpaul
Copy link
Collaborator

kmpaul commented Apr 2, 2019

There is already the https://github.com/pangeo-data/storage-benchmarks repository, which we can build on (possibly move into this repo). I think that these benchmarks should consider different formats:

  • zarr
  • hdf5
  • netcdf

And I think we need to compare these to their "idealized" use cases, which are independent I/O (i.e., each process reads/writes from/to its own file) for zarr and MPI-IO (each process reads/writes from/to the same file) for hdf5 and netcdf.

These benchmarks should be run on different platforms and storage systems (HPC with GPFS or Lustre, AWS S3, GCS, etc.).

What all do we need for this?

@rabernat
Copy link
Member

rabernat commented Apr 2, 2019

This repo has a lot of ideas to start from: https://github.com/rabernat/zarr_hdf_benchmarks

@andersy005 has been running it on Cheyenne

@kmpaul
Copy link
Collaborator Author

kmpaul commented Apr 8, 2019

@rabernat Thanks! I think this is very similar to the kinds of benchmarks that IOR conducts with C-based code. I have tried doing something similar with the Python code in the past, and I have not seen scaling. However, I have seen scaling with the C libraries. I don't know why this is, yet.

@kmpaul
Copy link
Collaborator Author

kmpaul commented May 21, 2019

Haiying Xu (@halehawk) now has a fork of IOR in the NCAR organization (NCAR/ior). I am going to have IOR scripts added to this repo and I/O results on Cheyenne using IOR/Z5.

tinaok added a commit that referenced this issue Oct 10, 2019
update Andersons change to my fork
@kmpaul
Copy link
Collaborator Author

kmpaul commented Feb 2, 2021

I believe some of this has been address by #44.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants