Actions
Story #6783
open
[Performance] Compare Collection performance benchmarks across components
Status:
New
Priority:
Normal
Assigned To:
-
Category:
Performance
Target version:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Story points:
-
Description
We now have performance numbers for common collection operations in the following components:
- API server
- Python SDK
- FUSE
- Workbench
Now that we have these numbers, the next step is to compare them and look for places where there are substantial, achievable performance improvements. We should be able to prioritize improvements based on which ones provide the most clock time savings based on development effort.
The outcome of this story should be implementable stories, with information about the expected time savings for each.
Updated by Brett Smith almost 9 years ago
- Description updated (diff)
- Category set to Performance
Updated by Ward Vandewege almost 3 years ago
- Target version deleted (
Arvados Future Sprints)
Actions