[...] Quite a few problems resulted in memory leaks, but one was particularly nasty: Squid processes under high load started leaking CPU cycles somewhere. After deploying profiling for squid we actually ended up seeing that the problem is inside libc. Once we started profiling libc, one of initial assumptions appeared to be true - our heap was awfully fragmented, slowing down malloc().The tcmalloc documentation is pretty detailed in describing how it works, too.
Here comes our steroids part: Google has developed a drop-in malloc replacement, tcmalloc, that is really efficient. Space efficient, cpu efficient, lock efficient. This is probably mostly used (and sophisticated) libc function, that was suffering performance issues not that many people wanted to actually tackle. The description sounded really nice, so we ended up using it for our suffering Squids.
The results were what we expected - awesome :)
tcmalloc
-
münchen
On that note: I'm living in Munich for the next week plus a few days. Do I know anyone around here? (PS: The LJ → PubSubHubbub → Reader…
-
deb/rpm diffing tools
Dear Linux hackers, Chrome tends to push minor updates (often security) pretty frequently. We'd like to operate as a good member of the Linux…
-
emacs
I've been using vim for a very long time -- over ten years -- but over those years I've envied more and more the way emacs integrates other software.…
- Post a new comment
- 28 comments
- Post a new comment
- 28 comments
-
münchen
On that note: I'm living in Munich for the next week plus a few days. Do I know anyone around here? (PS: The LJ → PubSubHubbub → Reader…
-
deb/rpm diffing tools
Dear Linux hackers, Chrome tends to push minor updates (often security) pretty frequently. We'd like to operate as a good member of the Linux…
-
emacs
I've been using vim for a very long time -- over ten years -- but over those years I've envied more and more the way emacs integrates other software.…
