Well, I had to check in on you guys.. ;) Could somebody please tell me where I asked for help? My intention was to let whoever made the scan process know that it has the possibilty of freezing at 99% for hours and hours.
I might have gone out on a ledge when i said that my system was the perfect setup. This might not be the case, but the key issue here is (as Patrick dixon said) that the slimserver scan process should be able to gracefully recover from these errors (like itunes and mediaplayer library). A playlist that loops, so what? As i said before, I'm sure there is a pattern for solving similar problems. KDF mentioned that all the error information is located in the logs. Well, if this is true, the developer certainly knew about the error, and why didnt he just fix it? Here are some other reasons why I thing the scan process might need some work: First of all, any program running on a desktop computer (in the background) that consumes 99% cpu (slimserver does this when working properly too) for more than 10 minutes will have a severe risk of beeing killed by the user which is never a good thing. Chances are that slimserver will be put into an inconsistent state. There are ways to tag a proc with a priority, giving other, more important procs the chance to breathe. Second, simply by looking at the thread count of the slim.exe process (2 threads) I'm guessing that the developer has choose a brude force approach to indexing the data. Slim probably uses on thread to listen for request on port 9000, and the second to perform fetch/index op. The brude force theory is further confirmed by the fact that the whole process seems unneccecarily slow. i/o ops (database and fileread) vs preprocessing of the data could surely be done in parallell. (Of course, i might be wrong, in that a threadpool might be in use) Last, but not least. Most operating systems today, and indeed indexers (google desktop, ms desktopsearch, spotlight, etc) , utilize Filesystemwatchers for realtime indexing. It is cheap and easy to implement (a couple of codelines in .net). This would certianly solve ModelCitizen's complains about indextime for adding only one new playlist item. And to mrSinatra, your response to the phrase "How much did you pay for the server software?", Originally Posted by pfarrell illustrated the point nicely. PS: I'm currently running 6.5 (alpha, beta, gamma or whatever) now...seems to be working...so maybe the intern is all grown up now. :P -- inv ------------------------------------------------------------------------ inv's Profile: http://forums.slimdevices.com/member.php?userid=6937 View this thread: http://forums.slimdevices.com/showthread.php?t=26350 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
