top | item 6285232

(no title)

adamlj | 12 years ago

It sounds very likely that it was Ruby that consumed so much of the CPU.

discuss

order

No comments yet.