I was looking at using Ploy to move a bunch of plots as a test. I configured it with multiple SOURCE drives and multiple DESTINATION drives.
When I launch it, it starts moving plots from only one drive but the same number of plots as my destination drives. This immediately saturates the drive and limits the transfer to the output of just that one drive.
Attempting to change ONE_PER_DRIVE from False to True causes it just to send a single plot at a time.
I am not sure if I misunderstood the thought process, I assumed to maximize drive throughput it would move plots one-at-a-time from each listed SOURCE to each listed DESTINATION. As it sits, I max out my single drive IO long before my 10 and 40GB links.
I got around this by running four different iterations with different settings each.
rjsears
commented
12 months ago
I was looking at using Ploy to move a bunch of plots as a test. I configured it with multiple SOURCE drives and multiple DESTINATION drives.
When I launch it, it starts moving plots from only one drive but the same number of plots as my destination drives. This immediately saturates the drive and limits the transfer to the output of just that one drive.
Attempting to change ONE_PER_DRIVE from False to True causes it just to send a single plot at a time.
I am not sure if I misunderstood the thought process, I assumed to maximize drive throughput it would move plots one-at-a-time from each listed SOURCE to each listed DESTINATION. As it sits, I max out my single drive IO long before my 10 and 40GB links.
I got around this by running four different iterations with different settings each.
Thanks