Leader of Birmingham.pm [pm.org] and a CPAN author [cpan.org]. Co-organised YAPC::Europe in 2006 and the 2009 QA Hackathon, responsible for the YAPC Conference Surveys [yapc-surveys.org] and the QA Hackathon [qa-hackathon.org] websites. Also the current caretaker for the CPAN Testers websites and data stores.
If you really want to find out more, buy me a Guinness
I've recently installed SLES 10.0 on my desktop at work. Unfortunately my first experience of it isn't good. The load average went sky high, and because of that it took nearly half an hour to open a terminal window to find out why. It turns out that a little app, that I've been hearing about from various Linux sources as being a new cool thing, is hogging the system like a mad thing. It's called Beagle.
If you've not heard of Beagle it's an indexing system. I'd forgotten how bad indexing systems are on performance, since I've been turning them off in Windows since I first encountered the Windows 95 abomination. They feel the need to install themselves by default and promptly scan everything, thus bringing your machine to it's knees.
Since finally managing to kill the Beagle process and uninstalling it, the performance has drastically improved. However, not as much as I would like. It seems the machine is still hitting swap on a regular basis and I noticed that X is using 156MB of virtual memory, which to me seems rather a lot. I guess there are some default plugins in there that I could remove, so I'm currently working through the system apps tailoring the settings to my liking.
I have to confess the main reason for trying SLES 10 was to try out Xgl, but with the performance I'm getting at the moment, I'm not so sure installing that would be a good idea. We'll see.