Sorry I wasn't a bit more clear in my opening post regarding some details.
I'm running with a real Squeezebox now. I thanked the Slim support team for handling the situation with UPS. UPS says they delivered the original package yet I received nothing. They had no signature because they said it was left at the front of the house. Nice job. In 2003 my car was stolen from the driveway while I slept. They thought they should trust the neighborhood with a US$340 package while no one was home (that's the price with shipping). I also wasn't accessing the web server from the same system. I've tested using a third system, a PowerBook G4 (my main workhorse), both with Camino and Safari and wired plus wireless connection. I no longer run Firefox as it's a huge bloated memory pig and so full of bugs that it's practically useless on a Mac. I also forgot to say that the Mini has 1GB of memory while the G4 had only 640MB, both running 10.4.8. I thought that the artwork would be generated during the build/scan but I have seen first hand that it's not (which is exactly what's been written in this thread by others). All the artwork in my music has been imbedded using iTunes 7.x and collected from various sources. The images range in size from 200x200 to 800x800 and probably average in the middle somewhere. The tracks are all stored neatly in their own album folders in a top-level hierarchy arranged by artist, so I wouldn't mind running some script to generate the required external images ahead of time. I have no doubt most of the time spent by the CPU is with the sql queries and I didn't mean to imply that the blame rested on the shoulders of the Perl implementation. But to call Perl fast has to be taken in context. Sure, it can be considered adequate in terms of a scripting/interpreted language, but look at the broader picture which includes compiled languages like C. Execution times of 100x faster for the same piece of code would not be uncommon. Whether speeding up portions or all of the current Perl modules would help the web serving performance drammatically is anyone's guess (I suppose anyone touching that code can comment with better hypothesis). But having some portions compiled would certainly not adversely affect runtime speed. So, how does one time the web interface as was briefly mentioned earlier in this topic? I'll try getting some numbers for various scenarios. -- MelonMonkey Bruno *'Twisted Melon - Fine Mac OS Software' (http://twistedmelon.com) | 'mira - Personal Control for your Apple Remote' (http://twistedmelon.com)* ------------------------------------------------------------------------ MelonMonkey's Profile: http://forums.slimdevices.com/member.php?userid=8466 View this thread: http://forums.slimdevices.com/showthread.php?t=30145 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
