ModelCitizen Wrote: > It's not solely a problem with Perl code performing badly on Windows > machines I saw no evidence of that. I can fire off at least 10s of requests per second to the slim server and it handles the interrupts and replies quickly.
> it's just that SlimServer is fundamentally flawed and needs some part of > the core rewriting. I wouldn't agree with that assessement either. I would say, from past experience with performance analysis of large pieces of code, that 99% of it is fine. There's 1% that may need some rewriting. Finding and identifying that 1% is often more work than the rewriting of it. > Robin Bowes was adamant that this should include making the application > multi-threaded. Unfortunately his suggestion was not taken up. In > retrospect it looks like it should have been. Again, I don't think that conclusion is supportable (at least not as far as I have looked into it). I read in another thread recently that someone broke it out into 2 threads fairly easily, and that solved almost all of the problem. I'm waiting to hear back from him what he did. But from what he described, the results sound plausable and the work achievable without huge expenditures of time and resources. Michael -- Michaelwagner _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
