[Bugs] [Bug 1623107] FUSE client's memory leak

bugzilla at redhat.com bugzilla at redhat.com
Thu Jan 3 06:06:23 UTC 2019


https://bugzilla.redhat.com/show_bug.cgi?id=1623107

Amar Tumballi <atumball at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|mchangir at redhat.com         |sunkumar at redhat.com



--- Comment #37 from Amar Tumballi <atumball at redhat.com> ---
> Unfortunately, the new version has a drawback - CPU time increased 2.5x
> times. At the moment it doesn't matter for us.
> Anyway, I'm sure this change solves our problem. And of course, we're
> looking forward to a stable version with it.

While a release with this patch merged/tested is another 50days away, we surely
would like to reduce the CPU load you see too. Whenever you get time, if you
can capture CPU info with below tool "perf record -ag --call-graph=dwarf -o
perf.data -p <pid of glusterfs process>", and then see "perf report" to see
what actually caused the CPU usage, it will help us to resolve that too.

Also note, lru-limit=10000 while many files are accessed may not be a good
value. I recommend something like 64k at least. But well, it depends on your
memory needs too. So, if you can give 512MB - 1GB RAM for glusterfs, its better
at least for performance.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the Bugs mailing list