Hi,
First of all congratulations for you development. It´s really good.
We have a customer that has a copy of all inbound and outbound mail in an account. When he tries to open the mail, the process of index all mail consume all cpu and memory. How can we avoid this kinds of things?
Thank you in advance, Lucas
- Lucas -LandM- lucas@landm.net:
Hi,
First of all congratulations for you development. It´s really good. We have a customer that has a copy of all inbound and outbound mail in an account. When he tries to open the mail, the process of index all mail consume all cpu and memory. How can we avoid this kinds of things?
Use dovecot's deliver program when delivering to that mailbox. This will keep the index up-to-date.
-- Ralf Hildebrandt (Ralf.Hildebrandt@charite.de) plonk@charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de Program aborting: Close all that you have worked on. You ask far too much.
Hi Ralf,
It would be great, but we have an LDAP+exim as backend, and searching in documentation doen´t seem so easy :( Is posible to call index directly instead as a part of delivery?
Thank you, Lucas
Ralf Hildebrandt wrote:
- Lucas -LandM- lucas@landm.net:
Hi,
First of all congratulations for you development. It´s really good. We have a customer that has a copy of all inbound and outbound mail in an account. When he tries to open the mail, the process of index all mail consume all cpu and memory. How can we avoid this kinds of things?
Use dovecot's deliver program when delivering to that mailbox. This will keep the index up-to-date.
First of all congratulations for you development. It´s really good. We have a customer that has a copy of all inbound and outbound mail in an account. When he tries to open the mail, the process of index all mail consume all cpu and memory. How can we avoid this kinds of things?
OS? How many messages? Maildir or mbox?
The index will have to be built, but maybe you can set it at a lower nice level?
Hi Charles,
RedHat 4.0, Maildir, 3 Gb. of volume, and about 6k msgs. Never finish the build task, could I force to exec the process for this user?
Thank you, Lucas
Charles Marcus wrote:
First of all congratulations for you development. It´s really good. We have a customer that has a copy of all inbound and outbound mail in an account. When he tries to open the mail, the process of index all mail consume all cpu and memory. How can we avoid this kinds of things?
OS? How many messages? Maildir or mbox?
The index will have to be built, but maybe you can set it at a lower nice level?
On Sat, 2007-06-16 at 14:04 +0200, Lucas -LandM- wrote:
Hi Charles,
RedHat 4.0, Maildir, 3 Gb. of volume, and about 6k msgs. Never finish the build task, could I force to exec the process for this user?
6000 messages isn't hardly anything. You didn't mention your Dovecot version. If it's 0.99.x, upgrade to 1.0.1 instead that that most likely solves the problem.
Hi Timo,
[root@hs-276 sbin]# ./dovecot --version 1.0.rc22
Do you recommend an update ?
Lucas
Timo Sirainen wrote:
On Sat, 2007-06-16 at 14:04 +0200, Lucas -LandM- wrote:
Hi Charles,
RedHat 4.0, Maildir, 3 Gb. of volume, and about 6k msgs. Never finish the build task, could I force to exec the process for this user?
6000 messages isn't hardly anything. You didn't mention your Dovecot version. If it's 0.99.x, upgrade to 1.0.1 instead that that most likely solves the problem.
On Sat, 2007-06-16 at 23:14 +0200, Lucas -LandM- wrote:
Hi Timo,
[root@hs-276 sbin]# ./dovecot --version 1.0.rc22
Do you recommend an update ?
That shouldn't contain any bad bugs. Do you use quota?
Could you strace the process while it's hanging (for a few seconds) and send me the output? http://wiki.dovecot.org/Debugging/ProcessTracing
participants (4)
-
Charles Marcus
-
Lucas -LandM-
-
Ralf Hildebrandt
-
Timo Sirainen