Symantec 10765539 Planning Guide - Page 35

Understanding system requirements 35 Factors that affect performance Warning: A typical entry in the Message Tracking Log occupies 800 bytes of storage space. While occasionally useful, message tracking can degrade system performance, especially when audit events must be logged and stored for high volume email traffic. You should use it judiciously. ■ Scheduled reports - Schedule reports for times when utilization is low. Also bear in mind that advanced reporting can impair performance. ■ Role of Control Center host - In cases where the Control Center host is also a busy Scanner host, the Scanner and Control Center must share the resources of a single machine, which may affect performance. Spam Quarantine and LDAP performance considerations Consider the following Spam Quarantine and LDAP performance implications. ■ Number of messages expected per day into Spam Quarantine - The more messages placed in the Spam Quarantine, the larger the database, and the more processing required. Reduce the maximum size of the Spam Quarantine database by deleting spam, or by reducing spam retention time. ■ Number of end users logging into the Spam Quarantine interface - More connections to end users results in more overhead for the system. Symantec recommends Spam Quarantine for user populations of 30,000 users or less. ■ LDAP server throughput - LDAP lookups for message recipients against a limited capacity LDAP server will severely impair Spam Quarantine and SyncService performance. Ensure that you have adequate capacity on your LDAP server, and/or consider creating a LDAP server replica. ■ Message queues - Because the Spam Quarantine database is stored on the Control Center, Spam Quarantine's SMTP server may slow down, causing the Scanner's delivery MTA to back up when the destination MTA is accepting messages either slowly or not at all. If this occurs, some legitimate mail messages may be delayed.