ni / ni/nisystemlink-clients-python
Downloading artifacts via ArtifactClient Python API is significantly slower than HTTP API
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10
- Forks
- 32
- Avg merge
- 12h 42m
- Merged PRs (30d)
- 2
Description
I have been working with Notebook Execution artifacts recently and have found that downloading takes MUCH longer using the Python API.
A ~120MB file took upwards of 24 minutes to download using the Python API while the HTTP API took about 6 seconds.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Python ArtifactClient download path and comparing it with the HTTP API behavior described in the issue. Reproduce the reported case with a roughly 120 MB Notebook Execution artifact and measure both approaches; done means the Python API download no longer has the reported severe slowdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100