On 8/3/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote: > randy roy ha scritto: > > When I first started with JAMES and MySQL, my mail load was pretty > > light. So I just used the default MySQL configuration and the default > > JAMES datasource configuration. Over the years, the amount of mail I'm > > processing has grown significantly. It has come to the point where > > MySQL is using 90-98% of the CPU, with the CPU pegged at 100% a lot of > > the time. > > First try this: > mysql> repair table spool; > mysql> repair table inbox;
The james tables are indexed but they are also normally empty, this seems to result in a large fragmented index, which reduces performance with time. no index at all is slower but performance is stable. You should rebuild the index regularly if you process large volumes of mail. (This is not specific to James/MySQL but it also a problem with other DB's and other scenarios where an indexed table is normally empty, e.g. I've seen the same behaviour from Oracle AQ queues) d. d. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
