|
|
Table of Contents
3.1. Generic Server Configuration 3.1.2. Other Generic Server Parameters 3.3. Connectivity and Threading 3.3.3. Threads 3.4.1.1.1. Basic Directory Setup 3.4.1.1.2. LDAP Entry Structure 3.4.1.1.3. LDAP Authentication 3.4.1.2. AXIGEN Mapping System 3.4.1.3. AXIGEN Authentication System 3.4.1.4. AXIGEN Front-End Services Setup 3.4.1.4.2. The IMAP and POP3 Proxies 3.4.1.5. AXIGEN Back-End Services Setup 3.4.2.1. Configuring Mapping Parameters 3.4.2.4. Webmail Proxy Service 3.4.3. AXIGEN LDAP Authentication 3.4.4. Integrating Active Directory into a cluster environment 3.5. Groupware and collaboration |
3.3.3. Threads
AXIGEN has a multi-threaded engine which allows separate module thread allocation. Combined with Linux OS multi processor capabilities, the multi-threaded engine can break server activity into multiple parallel processing threads. By allocating a number of threads to certain modules, (SMTP Receiving / SMTP Sending / WebMail / IMAP, etc.) resource (memory/CPU) distribution is adapted to usage scenario (main mail server / backup server / gateway mail server) and hardware resources.
Thread allocation is performed using the connection thread control parameters available for most AXIGEN modules. Depending on your network specifications and conditions the workload can be adapted to the server's processing power, in order to prevent a system overload and/or improve its performance. More details on connection thread management using WebAdmin are available in each service description tab. These parameters are also accessible for configuration in each service section from axigen.cfg (see Configuring AXIGEN using the Configuration File). You can also configure connection thread parameters in each service context from CLI, for more information please see Configuring AXIGEN using CLI. |
| Copyright © 2005-2008 Gecad Technologies | Site Map | Privacy Policy | Copyright Policy |