Memory usage seems better than in beta3. I have been building software
in a glusterfs volume for a few hours, and glusterfsd memory footprint
is still reasonable. And it did not crash.
There have been fixes checked in on that front, or I am just lucky?
--
Emmanuel Dreyfus
http://hcpnet.free.fr/p
On 03/09/2014 02:39 PM, Emmanuel Dreyfus wrote:
Memory usage seems better than in beta3. I have been building software
in a glusterfs volume for a few hours, and glusterfsd memory footprint
is still reasonable. And it did not crash.
There have been fixes checked in on that front, or I am just lu
Vijay Bellur wrote:
> Do not observe any fixes related to memory leaks. Would it be possible
> to get a valgrind report for the glusterfsd processes if you happen to
> observe the leak again?
Unfortunately, valgrind was not ported on NetBSD.
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...
Vijay Bellur wrote:
> Do not observe any fixes related to memory leaks. Would it be possible
> to get a valgrind report for the glusterfsd processes if you happen to
> observe the leak again?
I have the answer: I made a mistake reinstalling, and I am now running
3.5.0qa2 instead of 3.5.0beta4
T
On 06/03/2014, at 9:01 PM, Luis Pabon wrote:
> Hi all,
>The patch is now live in GlusterFS. This patch will allow you to write
> unit tests for your new patches or if you want, you can start writing unit
> tests for older code. Writing unit tests for older code is a great way to
> learn th
On 03/09/2014 04:17 PM, Emmanuel Dreyfus wrote:
Vijay Bellur wrote:
Do not observe any fixes related to memory leaks. Would it be possible
to get a valgrind report for the glusterfsd processes if you happen to
observe the leak again?
Unfortunately, valgrind was not ported on NetBSD.
In th
Hi Justin,
Do you have the logs for the build, or how to reproduce it? Let's
take this offline and see what we can do.
- Luis
On 03/09/2014 09:18 AM, Justin Clift wrote:
On 06/03/2014, at 9:01 PM, Luis Pabon wrote:
Hi all,
The patch is now live in GlusterFS. This patch will allow yo
Emmanuel Dreyfus wrote:
> > Do not observe any fixes related to memory leaks. Would it be possible
> > to get a valgrind report for the glusterfsd processes if you happen to
> > observe the leak again?
>
> I have the answer: I made a mistake reinstalling, and I am now running
> 3.5.0qa2 instead
Vijay Bellur wrote:
> 6. Noticing those allocations which have significant size & num_allocs
> in the output of grep can help in narrowing down the leak.
Here are the worst offenders for num_allocs:
[protocol/server.gfs35b4-server - usage-type 48 memusage]
size=17344060
num_allocs=408214
max_si
