Hi Chris, On Wed, Oct 18, 2006 at 07:01:07PM +0100, Chris Wilson wrote:
> of memory (due to Apache I think), pmacctd started spawning more threads > to write to the database. I ended up with 73 processes/threads in total, > almost all database writers. > > Is this really a good idea? Wouldn't it be better to serialise database > writes to some extent, to degrade gracefully rather than spiralling to > death? Or is this already possible and I missed the config option? If you see, such processes are not taking CPU, they are just laying out there. This is because they are all on their LOCK, waiting for the green light. LOCK serializes things: selects one of those processes, allows it to do its job and terminate, then selects another one, etc. You should avoid such a queue to come up. It might be related to the low specs box. But it might also be that you are not aggregating things that much (are you?). Take a look to the discussion happened on the list just earlier this month about database, performances, etc. Then, using MySQL, you can also take a look to the following configuration directives in CONFIG-KEYS: sql_dont_try_update and sql_multi_values. They usually help. Cheers, Paolo _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
