-
Notifications
You must be signed in to change notification settings - Fork 33
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
Chunking schema #135
Comments
@dnadeau4 I personally would be accessing the time axis first, as for most applications you want the temporal history rather than a single time slice |
Well, if chunk the data using Chunking with |
@dnadeau4 I really wonder whether this is a good idea, the performance hit is huge for making assumptions about how users are going to access the data.. The defaults look pretty good to me..
|
I could let
|
I should expose the "set cache size" as well... |
I have let the set chunking otherwise the default chunk is used. |
@taylor13 @durack1 @doutriaux1
I have been working on the "chunking" attributes and pushed in cmor-3.2.2 a new "chunking" schema.
It is very difficult to chose one schema that will satisfied everybody as you can see in this document.
chunking_data_why_it_matters
I decided to chunk following the
Spatial Access
cross section (see above link) since we usually access one level ofglobal
data over time. So the chunking will be (1,1,Ysize, Xsize) for (time, level, lat, lon)@ehogan Let me know how this impacts your file size, and if this is acceptable.
The text was updated successfully, but these errors were encountered: