Jump to content


Popular Content

Showing content with the highest reputation on 02/18/18 in all areas

  1. Yup, the ease of duplication was one of the main reasons I was attracted to DrivePool. Also, thank you; that clears things up: the "older parts" that will be deleted are the remaining parts of the damaged files, so that the intact copies can be re-replicated. Edit: I was going to mark your reply as the "best answer", but due to the architecture of this forum, that takes it out of the flow of the thread to be displayed at the top which I imagine would make it difficult to follow the conversation for anyone else. So I'll leave things as they are. Thanks!
    1 point
  2. From the UI, it looks like the file is being moved from the N:\ drive to another location on the N:\ drive, but isn't using "smart move". In this case, this fould be more normal, as the file system is both reading and writing to/from the drive. That means that the I/O is split between the two. In a best case scenario, this would halve the speeds, meaning you're really seeing closer to 70MB/s speeds here. But in reality, you may see worse than half, because of overhead (such as head actuation). So you may may have been getting 80-90MB/s or faster from the drive normally. As for this sort of prioritization, it's very hard to do, as determining this "on the fly" is complex and ... "expensive" (in terms of system resources). However, we do have the SSD Optimizer, which would help with this immensely. It's designed to create a write cache for new files. New files (like this) would be written to the "SSD" drive first, and then later balanced off to the other disks. This would split up the I/O load, and put the new files on the much faster drive, potentially boosting speeds.
    0 points
  • Create New...