Lauri Pesonen
Wed, 07 Jan 2009 12:55:13 -0800
I had another look and this and realised that I saw the issue also with a TCP server that was not serving any connection, i.e. none of the components that form the protocol handler were even instantiated. I also ran EchoProtocol().run() which also resulted in a small constant load. So it seems to me that the Axon/Kamaelia framework generates a small constant load even when idle.
The load is around 2.6% when the process starts up and then might or might not go down closer to 1%. -- Lauri 2009/1/5 Lauri Pesonen <lauri.peso...@iki.fi>: > 2009/1/3 Sylvain Hellegouarch <s...@defuze.org>: >> >> It's not normal indeed. Most likely, one of your component doesn't pause >> when it's not needed making the scheduler runs like crazy. Ensure you >> have somthing similar to: >> >> if not self.anyReady(): >> self.pause() >> >> yield 1 >> >> In every components. > > Thanks Sylvain, that makes me more comfortable using the framework. > I'll try locating the component that is not pausing appropriately. I > can say that it's not one of mine since they all have pausing in them, > but based on my experiences with DataChunker and Framer it seems that > the framework has some components that are not active developed and > they might be 'broken' when it comes to pausing. > >> - Sylvain > > -- > ! Lauri > -- ! Lauri --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "kamaelia" group. To post to this group, send email to kamaelia@googlegroups.com To unsubscribe from this group, send email to kamaelia+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/kamaelia?hl=en -~----------~----~----~----~------~----~------~--~---