Growing memory usage

[[email protected]…]

Here's a ticket to talk about the "growing memory use" problem. Using 0.8.0, I just ran the client on 62 nodes and saw this change in server memory usage:

Before:

root      2108  0.1  5.2 115444 108192 pts/11 S   Feb02   6:59 /usr/bin/python2.3 /usr/sbin/bcfg2-server

After:

root      2108  0.1  5.6 123176 115956 pts/11 S   Feb02   7:36 /usr/bin/python2.3 /usr/sbin/bcfg2-server

The only thing done between these data points is running the 62 clients. You'll also note that the beginning memory size is already quite a lot larger than the ~46MB we saw it using last week.

[desai]

Based on preliminary checks with valgrind, it looks like lxml is leaking memory like crazy. There is a new patch for lxml that seems to help; memory usage doesn't grow quite so quickly, but usage isn't flat yet. I am not sure this issue is resolved, so I am still leaving this open.

[desai]

It turns out that lxml has some other leak issues as well. I just sent a patch to the lxml list that should fix another aspect of the problem.

[anonymous]

another mail test

[anonymous]

one more mail test

[desai]

An upgrade to lxml-0.9 appears to have fixed this problem, except in the case of large package lists, which do not frequently change.