On Sat, 2 Apr 2005, Jack Coates wrote: > > FWIW, I get similarly poor performance with 6.0 on my setup, which I > > consider fairly hefty and underworked in general. I did get significantly > > improved responsiveness by changing the IO scheduler in 2.6 to cfq (don't > > even get me started on the horrible schedulers and vm in linux..) > > > > You know, that might be a factor; I've kept my kernel backported to 2.4 > for a lot of reasons. I also don't use shuffle much.
I had the same-ish issues under 2.4, I went to 2.6 fairly recently specifically to use the alternative schedulers, 2.2 was when I was last happy with linux vm stuff :) > what's your vmstat look like during a sort? Unfortunately, I'm not sure. The vmstat that comes with debian stable apparently doesn't like the new /proc structure that comes with 2.6, and promptly dies after starting it :) If I have to reboot for some other reason I'll boot into 2.4 and see what vmstat looks like. > > Maybe there's some perl library where older versions are significantly > > less efficient (but still work)? > > > > Possible, but Slimserver doesn't use many external versions; it > generally bundles its own modules. The only reason I even thought of this is because of a similar experience I had with mod_perl and mason trying to install request tracker a long time ago. If you were using 5.005 + some other older versions of a few modules, the web page would take *forever* to load. If you used 5.6 (then pretty new), it was fast. Apparently everyone who developed it just used 5.6 and had never tried with 5.005, because it was almost unusable :) > I've got just shy of 8K tracks on a mid-range home-brew server which is > fairly busy with other stuff. It's literally over a minute of 100% cpu usage (well, 95ish that it actually gets to use, but 100% of the cpu used) on this 2600+ when shuffle by album is selected with all the tracks, so I think there has to be something common in the setups or usage of some people that's absent from others that causes this. The startup scan (if I wipe the sql file before starting) is twice as long with 6.0 as well (1000s vs 2000s), it's almost all CPU time there as well. On the plus side, 6.0 uses about half the ram (65M currently after being up for a couple days). Moses _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
