Maximilian Roos

To put the relative speed of numpy access into perspective, I found this insightful: https://jakevdp.github.io/blog/2012/08/08/memoryview-benchmarks/ (it's now a few years out of date, but I think the fundamentals still stand)...

> Cython + memoryviews isn't quite the right comparison here. Right, tbc, I'm only referring to the top two lines of the pasted benchmark; i.e. once we enter python (even...

Great analysis, thanks Do we have any idea of which of those lines are offending? I used a tool `line_profiler` a while ago, but maybe we know already (I'm guessing...

TBC I think there's plenty we could do with relatively little complexity to speed up indexing operations on `DataArray`s. As an example, we could avoid the roundtrip to a temporary...

One note: if you're indexing into a dataarray and don't care about the coords, index into the variable. 2x numpy time, rather than 30x: ```python In [26]: da = xr.tutorial.open_dataset('air_temperature')['air']...

That's great that's helpful @nbren12 . Maybe we should add to docs (we don't really have a performance section at the moment, maybe we start something on performance tips?) There's...

Thanks for the ping @headtr1ck ! Any thoughts from others before we merge?

A small question to clarify: > > When the netCDF is unpacked using the nco command line tool, the correct values are unpacked. > ```python > $ xarray.open_dataset("BIG_FILE_unpacked.nc").ssrd.isel(time=slice(0, 23)).sel(latitude=44.8, longitude=287.1,...

Thanks. Does passing different values to `engine=` make any difference? I suspect the issue is at that layer.

This was v surprising behavior. Are there other similar libraries that share this? I haven't come across one