You're welcome, it's always the way. Please do post back if this does the trick. Here's a quick run down of the methods I mentioned;
Weighted Least Connections – Member & Node - This method load balances new connections to whichever Pool Member or Node has the least number of active connections, however, you define a Connection Limit (Weight) for each Pool Member or Node based on your knowledge of its abilities. The Connection Limits are used along with the active connection count to distribute connections unequally in a Least Connections fashion.
This method is suitable where the real servers have differing capabilities.
As each connection can have differing overheads (one could related to a request for a HTML page, the other a 20Mb PDF document that needs to be generated and downloaded) this is not a reliable way of distributing bandwidth and processing load between servers.
Member method: The weights and connection count for each Pool Member is calculated only in relation to connections specific to the Pool in question.
Node method: The weights and connection count for each Node is calculated in relation to all the Pools the Node is a Member of.
If all Pool Members have the same Connection Limit then this method acts just like Least Connections.
Dynamic Ratio – Member & Node - Also known as Dynamic Round Robin, this method is similar to Ratio but dynamic; real-time server performance (such as the current number of connections and response time) analysis is used to distribute connections unequally in a circular (Round Robin) fashion. This may sound like Observed but keep in mind connections are still distributed in a circular way.
This method is suitable where the real servers have differing capabilities.
Member method: The performance of each Pool Member is calculated only in relation to the Pool in question.
Node method: The performance of each Node is calculated in relation to all the Pools the Node is a Member of.
Observed – Member & Node - This method load balances connections using a ranking derived from the number of Layer Four connections to each real server and each server’s response time to the last request. This is effectively a combination of the Least Connections and Fastest methods.
Not recommended except in specific circumstances and not at all for large Pools.
Connections to each Pool Member are only considered in relation to the specific Pool in question.
Member method: The weights and connection count for each Pool Member is calculated only in relation to connections specific to the Pool in question.
Node method: The weights and connection count for each Node is calculated in relation to all the Pools the Node is a Member of.
Predictive – Member & Node - Similar to Observed but more aggressive as the resulting Pool Member rankings are analysed over time and if a Pool Member’s ranking is improving it will receive a higher proportion of connections than one whose ranking is declining.
Not recommended except in specific circumstances and not at all for large Pools.
Member method: The ranking and analysis for each Pool Member is calculated only in relation to connections and response times specific to the Pool in question.
Node method: The ranking and analysis for each Node is calculated in relation to connections and response times for all the Pools the Node is a Member of.