On Sat, Feb 23, 2008 at 06:12:26PM -0800, Jeff Cunningham wrote:
Zach Beane wrote:
Right. That's because not all threads are handlers, so the non-handler threads will signal an error. That code snippet is not very precise, and I just ignored the errors I got.
Zach
Okay - it's doing it right now. 99-100% cpu showing up as sbcl on my webserver user (the only sbcl running under that user). When I list out the notated threads I see the following. I'm not sure what I was expecting to see, but nothing stands out to me as a problem. All of them say "[finished & idle]". Can you interpret?
Nope, I got nothin'. The next thing I'd try, if I were you, is profiling all threads with sb-sprof to see where time is being spent.
Zach