> Instead of throwing more hardware at it, how about a software
> solution. Carl
> posted why mailman's archiving sucks. How about some of you
> Python guru's "fix"
> the performance issues?

Unless I'm missing something, Carl's diagnosis does not explain why the box
is I/O bound.  If the problem was caused by a concurrency issue as he
suggests, the box and/or disks would be not be fully loaded.

> As an aside, we are not the only group feeling the pinch. Lots of
> talk about
> performance problems, scalability of mailman on the mailman
> developer list.

So you blame the problem on mailman; not on an overworked box?

> I'd be willing to write the middle-ware and back-end stuff, if
> someone would
> work with me on designing the database to hold it all. Something
> like an open
> source www.geocrawler.com.
>
> So, time to put up or shut-up. Open source is about technical
> people solving
> their own problems (aka scratching their own itch). Seems like we
> got a big-ass
> mosquito bit. Who wants to help scratch?

I'd be happy to help with such an effort if a decent solution does not
already exist.  Are there not alternatives to mailman?

Mike