Project

General

Profile

Actions

Bug #4309

closed

[SDK] arv-copy collection copy performance

Added by Peter Amstutz almost 10 years ago. Updated 9 days ago.

Status:
Resolved
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Story points:
2.0

Description

Originally https://arvados.org/issues/3699#note-43

I'm copying a pipeline with a 5990M collection. I noticed this code:

                    data = src_keep.get(word)
                    dst_locator = dst_keep.put(data)

See attached image, there's a very clear falloff between blocks -- doing this sequentially isn't optimal. Download and upload could proceed concurrently. Also, it's possible we could get better utilization if we transferred multiple blocks at a time (e.g. 2x down / 2x up) by talking to multiple Keep servers. Consider a producer-consumer pattern using Python queues.


Files

arv-copy-perf.png (25.8 KB) arv-copy-perf.png Peter Amstutz, 10/24/2014 05:22 PM
Actions

Also available in: Atom PDF