-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Possible regression with PyNIO data not being lazily loaded #1720
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
Comments
@WeatherGod can you verify that you don't get immediate loading when loading netCDF files, e.g., with scipy or netCDF4-python? We did change how loading of data works with printing in this release (#1532), but if anything the changes should go the other way, to do less loading of data. I'm having trouble debugging this locally because I can't seem to get a working version of pynio installed from conda-forge on OS X (running into various ABI incompatibility issues when I try this in a new conda environment). |
Is there a convenient sentinel I can check for loaded-ness? The only reason
I noticed this was I was debugging another problem with my processing of
HRRR files (~600mb each) and the memory usage shot up (did you know that
`top` will report memory usage as fractions of terabytes when you get high
enough?). I could test this with some smaller netcdf4 files if I could just
loop through the variables and assert some sentinal.
…On Thu, Nov 16, 2017 at 8:57 PM, Stephan Hoyer ***@***.***> wrote:
@WeatherGod <https://github.com/weathergod> can you verify that you don't
get immediate loading when loading netCDF files, e.g., with scipy or
netCDF4-python?
We did change how loading of data works with printing in this release (
#1532 <#1532>), but if anything the
changes should go the other way, to do less loading of data.
I'm having trouble debugging this locally because I can't seem to get a
working version of pynio installed from conda-forge on OS X (running into
various ABI incompatibility issues when I try this in a new conda
environment).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1720 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AARy-MO7la8KSJnQoto8Kso5gBYedUKQks5s3OgSgaJpZM4Qflk->
.
|
The private Are you using dask to load this data? That can also change things. |
I don't think we have tests of this case for any backend other than |
OK. Found a bug and sent a PR. |
Awesome! Thanks! |
@WeatherGod reports on the mailing list:
The text was updated successfully, but these errors were encountered: