Comprehensive data protection for all workloads
Post Reply
JimmyO
Enthusiast
Posts: 55
Liked: 9 times
Joined: Apr 27, 2014 8:19 pm
Contact:

Merge performance and backup block size

Post by JimmyO » Mar 23, 2015 7:00 am

Gostev: in reference to you statement:
Gostev wrote:I've also noted that the job is using the smallest block size (256KB), which immediately means 4 times slower backup file processing than with the default settings, but this is not important as this would not change the processing speed between v7 and v8, so this is just FYI.
- Does this mean that the merge takes twice as long if you run "LAN Target (512KB)" (wich I do) than if I´d run "Local target (1024KB)" ?

Today my merge takes around 40 hours, forcing med to have multiple jobs for all VM:s...

Gostev
SVP, Product Management
Posts: 24612
Liked: 3463 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Merge performance and backup block size

Post by Gostev » Mar 23, 2015 2:59 pm

That is correct. 2x smaller block size = 2x more blocks to process = 2x more I/O operations, while storage IOPS capability is what exclusively defines random I/O workload performance.

Post Reply

Who is online

Users browsing this forum: Baidu [Spider] and 27 guests