Project

General

Profile

Actions

Idea #6783

open

[Performance] Compare Collection performance benchmarks across components

Added by Brett Smith over 9 years ago. Updated 8 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Performance
Target version:
Start date:
Due date:
Story points:
-
Release:
Release relationship:
Auto

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.

Actions #1

Updated by Brett Smith over 9 years ago

  • Description updated (diff)
  • Category set to Performance
Actions #2

Updated by Ward Vandewege over 3 years ago

  • Target version deleted (Arvados Future Sprints)
Actions #3

Updated by Peter Amstutz over 1 year ago

  • Release set to 60
Actions #4

Updated by Peter Amstutz 8 months ago

  • Target version set to Future
Actions

Also available in: Atom PDF