This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hello Dave, I would recommend option 3, as it provides the most fine-grained control over the chunking performance. You might also be interested in the following blog posts: * http://www.unidata.ucar.edu/blogs/developer/entry/chunking_data_why_it_matters * http://www.unidata.ucar.edu/blogs/developer/en/entry/chunking_data_choosing_shapes I hope this helps! -Ward > > When I read this page: > http://www.unidata.ucar.edu/software/netcdf/docs/netcdf_perf_chunking.html > > I see 3 options for improving the chunk performance: > > 1. change the configure script > 2. change the default chunk cache size, use the set_chunk_cache > function before opening the file with nc_set_chunk_cache() > 3. change the per-variable cache size, use the set_var_chunk_cache > function at any time on an open file > > Is there an option you suggest over the others? Option 3 looks the best > to me, as long as it's easy to get the chunk info for the variable. > > Thanks, > Dave > > On 5/26/16 9:54 AM, Unidata netCDF Support wrote: > > David Santek, > > > > Your Ticket has been received, and a Unidata staff member will review it > > and reply accordingly. Listed below are details of this new Ticket. Please > > make sure the Ticket ID remains in the Subject: line on all correspondence > > related to this Ticket. > > > > NOTE: All email exchanges with Unidata User Support are recorded in the > > Unidata inquiry tracking system and then made publicly available through > > the web. If you do not want to have your interactions made available in > > this way, you must let us know in each email you send to us. > > > > Ticket ID: PMM-566115 > > Subject: Chunking and performance > > Department: Support netCDF > > Priority: Normal > > Status: Open > > > > > > > > The NetCDF libraries are developed at the Unidata Program Center, > > in Boulder, Colorado, funded primarily by the National Science Foundation. > > > > All support requests are handled by the development team. No dedicated > > support staff are funded at this time. For this reason we cannot guarantee > > response times, nor that we can resolve every support issue, although we > > do our best to respond within 72 hours. > > > > It is in the nature of support requests that the same question is asked many > > times. We urge you to search the support archives for material relating to > > your support request: > > > > http://www.unidata.ucar.edu/search.jsp?support&netcdf > > > > If you are having trouble building netCDF, please take a look at the > > "Building NetCDF" page: > > > > http://www.unidata.ucar.edu/software/netcdf/docs/building.html > > > > or the (unfortunately somewhat out-of-date) NetCDF Build Troubleshooter > > page: > > > > http://www.unidata.ucar.edu/software/netcdf/docs/troubleshoot.html > > > > Windows users should see the FAQ list: > > > > http://www.unidata.ucar.edu/software/netcdf/docs/faq.html#windows_netcdf4_2 > > > > Complete documentation (including a tutorial, and sample programs in C, > > Fortran, > > Java, and other programming languages) can be found on the netCDF > > Documentation page: > > > > http://www.unidata.ucar.edu/software/netcdf/docs/ > > http://www.unidata.ucar.edu/software/netcdf/examples/programs/ > > > > If you resolve your issue through one of these methods, please send a reply > > to > > this email, letting us know that you no longer need support. This will help > > us spend more time on netCDF development. > > > > Best regards, > > > > Unidata User Support > > > > > Ticket Details =================== Ticket ID: PMM-566115 Department: Support netCDF Priority: Normal Status: Closed