Jump to content
Covecube Inc.

Search the Community

Showing results for tags 'speed'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Covecube Inc.
    • Announcements
  • StableBit Cloud
    • General
  • StableBit Scanner
    • General
    • Compatibility
    • Nuts & Bolts
  • StableBit DrivePool
    • General
    • Hardware
    • Nuts & Bolts
  • StableBit CloudDrive
    • General
    • Providers
    • Nuts & Bolts
  • Other
    • Off-topic
  • BitFlock
    • General

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. I recently added a shucked 12TB WD Elements drive and added it to a four bay enclosure connected to my PC via USB3. Before shucking, I ran several tests and confirmed that the drive is in good condition without any errors. However, once I added it to my current pool, I quickly noticed that balancing is incredibly slow in the range of 10-20 MB/s while also sending the drive's activity to 100%. What's strange is that it will typically start around 70-90 MB/s (and drive activity to about 60-70%) and after roughly one minute, the speeds plummet down. I have several terabytes of Linux ISOs to
  2. Dear true humans at Covecube, I have a stringent question that has been haunting me for weeks now: I currently have 11 physical HDD/SSD media that are all part of just ONE pool (and hence represented by one drive-letter..). Assuming I have lots of RAM free, and lots of CPU cores doing very little; Does this setup make sense, performance-wise, or is it faster or otherwise smarter to create more than one pool, say, for different directories or using different policies? I have a lot of placement rules active on this one pool, and lots of levels of multiplication set for diffe
  3. In Windows when deleting something like 100,000 files, it's quick and completes in a few seconds. This is a high-level delete operation. IO operations with Drivepool all take a much longer time than Windows. Things such as: In explorer: Right-click folder > properties (to view number of files, folders, size) OK, I'm not sure this one is drastically slower (if at all). Discovery takes a long time for a delete. Like #1 above. A delete operation take a long time for a large number of files. I'm talking like 50-150 IOPS, which makes me think this is re
  4. I'm just starting to experiment with DrivePool, and I'm wondering how best to use it to optimize for speed. I've got the following disks SSD 256Gb boot/OS SSD 512Gb working drive - photography 1st tier HD 4Tb fastest - photography 2nd tier tier HD 1Tb ok - replication / read cache HD 1Tb ok - replication / read cache HD 2Tb slow - archive HD 2Tb slow - archive For the moment I'm just using drivepool for the spinning rust disks... and will use Samsung RAPID for my working drive - so that's out of scope for now. The rest can be in the pool - but by default * when I s
×
×
  • Create New...