Robert Banz a écrit :
I don't have any system log that complains about something and the
only
Cyrus message I got is a DB4 warning about lockers. I think the DB4 in
question is the TLS sessions cache DB and in my case the number of
lockers can be as high as 8 000...
Dump Berkeley DB with
Alain Spineux a écrit :
On Mon, Apr 28, 2008 at 11:31 PM, Eric Déchaux [EMAIL PROTECTED] wrote:
Dear all,
I have juste setup a Cyrus infrastructure based on VMware Virtual
Infrastructure 3.0.1 and I have a huge performance problem.
The new infrastructure was sized for 120 000
Eric Déchaux [EMAIL PROTECTED] wrote:
I would have loved to put Solaris, Zones and Massaging Server here but it
was not a possibility. Custorme chose was VMware + Linux + Cyrus.
Just as a sidenote:
As closed source is not an option here, we use cyrus imap 2.3.12 on Solaris
and not messaging
On current production platform the frontends use swap massively but the
impact is far less than on the new platform.
It's not so much how much swap is actually used, but how much is being paged
in or paged out at any time. If there are memory pages not being used at
all, the OS will swap
Pascal Gienger a écrit :
Eric Déchaux [EMAIL PROTECTED] wrote:
The older infrastructure can stand the 42 000 concurrent sessions, the
new one can't : I was expecting each frontend to be able to handle 5 500
concurrent sessions but they are not. Around 3 000 / 3 500 concurrent
sessions the
Rob Mueller a écrit :
On current production platform the frontends use swap massively but the
impact is far less than on the new platform.
It's not so much how much swap is actually used, but how much is being paged
in or paged out at any time. If there are memory pages not being used
On Tue, 29 Apr 2008, Eric Déchaux wrote:
Pascal Gienger a écrit :
Eric Déchaux [EMAIL PROTECTED] wrote:
The older infrastructure can stand the 42 000 concurrent sessions, the
new one can't : I was expecting each frontend to be able to handle 5 500
concurrent sessions but they are not. Around
Robert Banz a écrit :
I don't have any system log that complains about something and the
only
Cyrus message I got is a DB4 warning about lockers. I think the DB4 in
question is the TLS sessions cache DB and in my case the number of
lockers can be as high as 8 000...
Dump Berkeley DB
Dear all,
I have juste setup a Cyrus infrastructure based on VMware Virtual
Infrastructure 3.0.1 and I have a huge performance problem.
The new infrastructure was sized for 120 000 mailboxes with 42 000
maximum concurrent IMAPS sessions (neither POP3 nor IMAP available). The
important point
I don't have any system log that complains about something and the
only
Cyrus message I got is a DB4 warning about lockers. I think the DB4 in
question is the TLS sessions cache DB and in my case the number of
lockers can be as high as 8 000...
Dump Berkeley DB with a quickness, and
On Mon, Apr 28, 2008 at 11:31 PM, Eric Déchaux [EMAIL PROTECTED] wrote:
Dear all,
I have juste setup a Cyrus infrastructure based on VMware Virtual
Infrastructure 3.0.1 and I have a huge performance problem.
The new infrastructure was sized for 120 000 mailboxes with 42 000
maximum
Eric Déchaux [EMAIL PROTECTED] wrote:
The older infrastructure can stand the 42 000 concurrent sessions, the
new one can't : I was expecting each frontend to be able to handle 5 500
concurrent sessions but they are not. Around 3 000 / 3 500 concurrent
sessions the frontends begin to SWAP and
12 matches
Mail list logo
