Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[FEATURE] Benchmarking memory

See original GitHub issue

🚨🚨 Feature Request

Related to an existing Issue
A new implementation (Improvement, Extension)

We should benchmark memory usage when fetching from a Hub dataset.

If your feature will improve `HUB`

In the near term, well-scoped memory benchmarks will assess new features. In the long term, it can be used to compare performance with other libraries such as Zarr and Tile.

Description of the possible solution

We could start with a client-side benchmark reading from a local volume, perhaps with memory-profiler.

Issue Analytics

State:
Created 3 years ago
Comments:25 (25 by maintainers)

Top GitHub Comments

2reactions

mynameisvinncommented, Feb 2, 2021

@haiyangdeperci is on top of things per usual

1reaction

haiyangdepercicommented, Mar 2, 2021

@KrishnaChaitanya1 can you send in the entire code in the form of a PR? It would be easier for us to review that. I assume you are running this with cache variable equal to False and then True. That’s all right. We need to gather these results in some readable format so you may include that as well. If you need more support, come to the benchmark call tomorrow, the team and other community members will help you out.