Thanks, Harris.
I tried it without io-threads to see what that would result in:
7218 root 17 0 476m 464m 844 R 85 23.0 41:15.20 [glusterfs]
It did increase a lot slower this time, but still nowhere near your numbers.
I'll see what happens when disabling one of read-ahead and write-behind, and
then both. I'd like to know where this memory usage comes from, because I
don't think I can deploy it like this yet.
I'm on 275, btw.
Rhesa
Harris Landgarten wrote:
Rheas,
My setup is very similar to yours but I am not using io-threads on the client (only on servers) and I have 2 bricks. This is my top
4522 root 15 0 14812 5420 848 S 0.0 0.3 0:11.03 glusterfs
Quite a difference.
Harris
----- Original Message -----
From: "Rhesa Rozendaal" <gluster@xxxxxxxxx>
To: "gluster-devel" <gluster-devel@xxxxxxxxxx>
Sent: Thursday, July 5, 2007 10:57:41 AM (GMT-0500) America/New_York
Subject: memory usage (client)
Hi guys,
I've been trying to limit glusterfs' memory consumption, but so far not much luck.
here's a snapshot of my "top":
6697 root 15 0 369m 295m 876 S 45 14.6 3:10.13 [glusterfs]
And it keeps growing, so I'm not sure where it'll settle. Is there anything I
can do to keep it to around 100m?
