Hi Dude!
Increasing more memory (both physical and SWAP) is always a good idea to improve
performance. DNS responses could be another factor that effect SWA performance. I
assume you increased Tomcat/Java memory by editing value for JAVA_OPTS in
/var/opt/scalix/s4/tomcat/bin/setclasspath.sh file.
What Scalix version you use, what is the current value for IMAP_CONNECTION LIMIT
and IMAP_CONNRATE_LIMIT. If you are using Scalix 11, did you upgrade from Scalix 10?
On searching Scalix knowledgebase, I could find that ideal values for IMAP_CONNECTION LIMIT
and IMAP_CONNRATE_LIMIT could be:
IMAP_CONNECTION_LIMIT=500
IMAP_CONNRATE_LIMIT=10
Note: The above settings will make IMAP connection and connection rate unlimited.
Running
should indicate how many connections you currently have.
There is a description about IMAP_CONNECTION LIMIT and IMAP_CONNRATE_LIMIT in
Scalix Administration guide.
IMAP_CONNECTION LIMIT, specifies the maximum number of concurrent IMAP
connections that the Server can support. If left at 0 (the default value), the IMAP4 Server
will continue to accept all connections until machine resources are exhausted. This
could adversely affect Scalix performance and eventually prevent other users from
accessing the Scalix Server.
IMAP_CONNRATE_LIMIT, specifies the maximum number of IMAP connection requests
that the IMAP Server will accept in any one second. If left at 0 (the default), the IMAP
Server will accept connection requests at a rate that is limited only by machine
resources. This could adversely affect Scalix performance and eventually prevent
other users from accessing the Scalix Server. If, for example, you set this value to 3,
the IMAP Server will be able to accept up to 180 connection requests per minute, and
machine resources should still be sufficient to allow normal Scalix operation.
Thanks,
Subir