I'm happy somebody finally brought this up. And I'm not yet convinced that the use of a temporary file will solve the scalability issue (and the issue is bad: number of connects per second increase with the number of clients, length of the XML file grows as well). After all you're writing XML out unnecessarilly often. Wouldn't it be better to have a central daemon keeping the data in memory and just responding to queries from the GUI instead of just rewriting a file so many times per second?
Regards, Erich On Wednesday 02 August 2006 17:01, Andrea Righi wrote: > wow! are you monitoring 50 clients? :-) have you tested the bittorrent > transport? > > Anyway the use of a temporary file seems reasonable, but have you tested > it or it's an hypothesis? do you have already a patch? > > Thanks, > -Andrea > > Matt Jamison wrote: > > I'd like to suggest the following change in si_monitor, after some heavy > > duty > > pounding... > > > > Rather than opening (truncating) the xml databasefile directly on each > > update, how about writing to a tmp file and then renaming the tmp file over > > the top of the actual database? With just 50 simultaneous clients, the > > truncation is quite noticeable. PERL's rename should be used to make the > > update atomic... > > > > Thanks, > > > > Matt ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sisuite-devel mailing list Sisuite-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-devel
