Swift/ideas/object-copy-between-object-servers
< Swift | ideas
Revision as of 08:38, 15 January 2018 by Romain.le-disez (talk | contribs) (Created page with "== Problem == When a proxy-server executes multiple COPY requests, its network interface bandwidth can easily saturate in case of replica policy. For an EC policy, it can cons...")
Problem
When a proxy-server executes multiple COPY requests, its network interface bandwidth can easily saturate in case of replica policy. For an EC policy, it can consume a lot of CPU power.
Example: with a 10Gbps NIC and a 3-replica policy, reading at 1Gbps, writing at 3Gbps, only 3 COPY can happens at the same time without contention.
Proposed solution
The object copy could take place directly between object-servers. I guess there is generally more network capacity at object-servers than at proxy-servers.
For replica policy, each replica could be copied to the corresponding object-server. For EC policy, each fragment could be copied to the corresponding object-server
Contact: rledisez on IRC
