On Wednesday 02 August 2006 20:33, Andrea Righi wrote: > Erich, > > thanks for the simulator! from a quick test it seems that the fs > overhead is quite high... for example moving clients.xml in /dev/shm > strongly reduce the load and cpu time of si_monitor and si_monitortk.. > so the idea to move the data in RAM seems reasonable..
Good! /dev/shm would probably already help a lot. But not writing at all would be even better, still for that you need some IPC method between the receiver threads and the master thread. pipes seem to be the simplest tom implement. BTW: You are sending two requests right behind each other. One for status and one for speed. Each triggers a write. Guess you could easilly extend the protocol to save one ;-) Regards, Erich > > -Andrea > > Erich Focht wrote: > > Here's a small simulator which doesn't simulate the impact of sending the > > logmsg to the master, and also you won't feel the impact of rsync daemons > > and > > such. But it give you an idea on what's happening. I see more than 50% user > > time with 50 clients, but my master might be quite small... And all > > requestes > > come from one host, that is unreallistic, too. > > > > Regards, > > Erich > > > > PS: Usage: ./clientsim.pl <no_of_clients> <monitor_host> <monitor_port> > > ------------------------------------------------------------------------- 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
