<P>Hi</P> <P>We use Mercury/32 V4.74 and Pegasus Mail V4.70. Mercury is installed on a Dell server running Windows Storage Server Standard 2008 (64bit). This server is a file server and hosts 99% of our data. Pegasus Mail is installed on the same server and the account folders are located as subfolders beneath the ..\pmail directory.</P> <P>The server is a member server in a Windows Active Directory domain. The domain clients access Pegasus Mail via a link to the installation on the server (i.e. Pegasus Mail is not installed on any of the client computers).</P> <P>The server has been running at near capacity with memory etc so I am doubling the amount of RAM in the system from 6 to 12GB and am also going to team the Broadcom NIC's. At present just one NIC is used. I will be enabling a second NIC and teaming them for smart load balancing use.</P> <P>Whilst researching this I have read that whilst the receiving and sending of data will benefit from more efficient routing of traffic across the NIC's, some applications may not work as well as when using just one NIC. This is because although the Broadcom Program takes the load off the CPU some applications that are CPU bound may actually suffer performance degradation in a smart load balancing setup.</P> <P>My question is: has anyone implemented SLB using Broadcom's application on a server where Pegasus Mail is installed and where clients link to the central installation? Did you notice any performance hits - did Pegasus Mail behave poorly, did you see an improvement or did performance remain unchanged?</P> <P> Any insights etc gratefully received.</P> <P>Thanks.</P>