New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
Glusterfsd requires a fair bit of memory for what it does. I would doubt it has been optimized or tested in such a low memory environment.
Give it at-least 256mb, preferably 512mb if you plan to have more than probably ten thousand files.
Our nodes (with only a few thousand files) run on 512mb ram (using 60%) without issues.
Hi,
alright. Maybe I'm just going to try it out.
The amount of files will be around 100-200 (encrypted tar-archives) so that should be easy to handle.
Afaik Ramnode offeres a refund within the first couple of days.
Thanks,
gehaxelt
It runs on 128 MB, although it might crash often. A daemon like supervisord helps to fix that issue.
You can however not do anything else on the vps or you will get oom errors. Been there, done that.
Hi,
yeah it seems like you're right.
I ran the following script on one of my nodes: https://raw.githubusercontent.com/pixelb/ps_mem/master/ps_mem.py
So you'll at least need about 256mb.
I think the server side of glusterfs can't be run on openvz (while the client mount side works).
Hi,
the serveride can run on openvz if the "fuse"-module is loaded. I don't know why the serverside shouldn't be working then.
As I said above, I'll try it and post the result.
Just my experience and the result of my googling. There are other posts about glusterfsd and openvz on this forum too.
But if you get a success I would like to know because I'm interested. So thank you for trying and posting your results.
128MB is too small.
Can you please stop posting useless comments? The majority of your posts are a few words with no real contribution and it's starting to annoy me and most likely others.
I feel an offer post coming.
I'm sorry, but that is what I wanna say.
You can always test it with a virtual machine on your own hardware with Virtualbox or VMWare Player, or another simple to use desktop virtualization software.
Then you know the size of the VPS you need.
I think he is more like spamming his signature for "SEO" purposes....I remember seeing some SEO sites mentioned before that the more link you have on the internet the better ranking it is (which is obviously false but people seems to buy it).
He has way passed his post count to post an offer.
Its not exactly false but a little more complicated than what he is doing.
Hi, excellent idea!
I'm not sure how I could have missed it.
Going to install openvz in a virtual machine and then create several 128mb glusterfs-openvzs.
Okay, here's an update:
One option could be to patch the sourcecode to use the user.*-namespace before compiling it:
I'm going to test that now.
Update:
So I compiled the newest release (3.5.1) from source applying the above listed "patch" and it works fine. At least I haven't noticed any errors. @a_chris
However, I still need to figure out if 128mb RAM is enough. Regarding to the GlusterFS documentation it should not be a problem: http://gluster.org/community/documentation/index.php/High_Memory_Usage