When deleting multiple blocks the network usage is suboptimal since each block
is deleted with a single delete request. It would be more effient to make a
single delete request with multiple objects (reference
http://docs.aws.amazon.com/AmazonS3/latest/API/multiobjectdeleteapi.html).
The --erase flag is the most impacted scenario, but normal usage (where
filesystem is mounted with discard) could also get a boost (eg rm -rf
/this/folder, or when deleting big files).
Another quirk seems to be the "max-keys" parameter of the GET /?marker.... http
request (that is actually fixed at 256). It would be better to make it an
option in the command line, and set its default to the system maximum (1000).
This gives network efficiency during the initial block listing.
Original issue reported on code.google.com by natalega...@gmail.com on 14 Jun 2015 at 9:47
Original issue reported on code.google.com by
natalega...@gmail.comon 14 Jun 2015 at 9:47