So I have this app… And it appears to be misbehaving. I can’t tell quite what it is blocking on (or momemtarily pausing on) as the case may be just by staring at top or its log files. It’s supposed to perform around 300 message submissions per second and appears to be doing like 30. So, where’s the problem? Or more importantly, how do we find the problem?
DTrace is the right answer of course, but I’m on Linux and FreeBSD here.
So a panic is a panic, right? Well yes in that is stops your server dead in its tracks, but the how you deal with it is the important thing. I’ve been frustrated for a long time with Linux and FreeBSD (Linux more so) regarding the lack of good post-mortem crash analysis facilities.Some background might be helpful here. One of the clusters that my company administrates has 10 FreeBSD 5.3, 1 FreeBSD 5.
It was a pleasure speaking at OSCON2005 on Wednesday on the topic of cross-vendor database replication approaches. Many attendees requested that I put the slides online. While there is a tremendous amount of commentary and critique that goes with the slides, I hope that they will be somewhat useful to a more general audience. Alas, here they are: DB Replication PDFDB Replication Keynote stack
