-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config path for database storage #1265
Comments
Which volume index are you using? memory or leveldb? Well, yes, there will be two writes, one to .dat and one to .idx files. If in memory, seems no need to store the index on SSD specifically, especially for reads. |
Leveldb. |
In your case, how large are the SSD and HDD sizes respectively? |
we store 5TB of data. |
ok. btw: planning to support ssd-only volumes. it is different from your request. would that be useful to your use case? |
Should be configurable:
So users can choose what suits them better. |
Added this feature. Let me know how it works for you. When starting volume server, use |
fixed in 2.13 |
We store the files on a shared drive (cifs mounted).
We have local SSD drives.
Would like to specify the
weed volume
server to used an alternate folder for database storage.So instead of storing .idx files on the network drive, store them local on fast SSD.
The text was updated successfully, but these errors were encountered: