[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 961108: netcdf I/O question

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.

  • Subject: Re: 961108: netcdf I/O question
  • Date: Fri, 08 Nov 1996 14:09:52 -0700
>To: address@hidden
>From: Jim Barbour <address@hidden>
>Subject: netcdf I/O question
>Organization: NOAA/FSL
>Keywords: 199611081713.AA09064

Hi Jim,

> I am trying to get a sense of how NetCDF's I/O works.
> 
> o Does is use stdio or unix I/O (open, read, write, etc.)

It uses POSIX I/O, which is the standardized name for Unix I/O, except
that it's supported on non-Unix systems: open, read, write, lseek, ...

> o Does it typically do large os small reads?

It tries to buffer I/O somewhat, by determining a preferred I/O block
size.  If a preferred block size isn't available, it just uses 8192 byte
buffers.

For more details, see the file netcdf/src/libsrc/posixio.c in the
distribution of the C-language-only alpha release at

    ftp://ftp.unidata.ucar.edu/pub/netcdf/netcdf-3.1a.tar.Z

--Russ

_____________________________________________________________________

Russ Rew                                         UCAR Unidata Program
address@hidden                     http://www.unidata.ucar.edu