Jump to content

Middge

Members
  • Posts

    6
  • Joined

  • Last visited

Posts posted by Middge

  1. 17 hours ago, Christopher (Drashna) said:

    we don't support using the Pool as a cache drive, by default.  This is because the cache is stored as a single large file. 

    it's not recommended, for a number of reasons.   Such as, the cache files will always be in use, and never be able to be balanced.  This can cause issues in some configurations. 

     

    But if you really must do this:
    http://wiki.covecube.com/StableBit_CloudDrive_Advanced_Settings#Settings.json
    Set "CreateDrive_AllowCacheOnDrivePool" to "True" and reboot the system. 

    So, I looked in "C:\ProgramData\StableBit CloudDrive\Service" and "C:\ProgramData\StableBit DrivePool\Service". Neither folder contains a "settings.json" file. I even checked the entirety the disk and there is not a file named "settings.json" anywhere.  :-(

    Am I missing something?

  2. Hello again!

    Recently I recreated my clouddrive, and I wanted to use my Stablebit DrivePool disk (two seperate SSD drives in a pool) as the cache drive for my Clouddrive disk. Unfortunately, it's not an option in the drop down window when choosing a cache drive. Is there a reason for this, or am I missing something?

  3. Hey all, long time user of Clouddrive here.

    A long long time ago (a year or two ago?) back when Clouddrive was in beta, I bought the product and began using it. It met almost all of my expectations and exceeded others. I use clouddrive to store media like most others here and I've stored almost 80TB thus far.

    Here is my problem,

    I created the drive using a very early beta, and I think my disk is actually suffering for this. It seems to get worse as I store more data. I want to start over, but this time I want to make sure I do it right. Is there any document or guide somewhere that can tell me the best practices for my use-case? That is, streaming high quality HD media over 10-20 concurrent connections with 1gbps symmetrical bandwidth. What chunk size should I use? What about cache size and prefetching?

    My current setup is as follows;

    10MB chunk size (i was wondering if I should increase to 20MB?)

    1MB prefetch trigger

    20MB prefetch size (should this match chunk size?)

    240 seconds prefetch time window

    20 upload threads

    20 download threads

    Background I/O: DISABLED

    50GB Cache on SSD (Should I increase this? I can probably afford up to 500GB SSD cache)

    Drive was formatted as NTFS (Should I use REFS? i am leary of this as refs has higher overhead and little recourse in the event of failure)

    Any help that you guys could provide would be greatly appreciated. Thanks in advance for your time.

×
×
  • Create New...