MySQL ASP Sessionstate (3 replies)

Our websites have reached a limit of the server they're sitting on and I want to spread them over multiple servers, but they use session state.

I've setup MySQL5.5 as a Master-Master replication on the web nodes and pointed the session to the "localhost" mysql server. The replication works fine and in testing you can move from one server to the other without issue. However, when it comes to putting the website under load (even a couple of hundred users) the MySQL becomes a real bottleneck and can't cope even thought the resources are minimal.

The connection string i'm using is

<connectionStrings>
<remove name="LocalMySqlServer" />
<add name="LocalMySqlServer" connectionString="database=ASPSession;server=localhost;Maximum Pool Size=100;Minimum Pool Size=10;pooling=True;Cache Server Properties=True;Connection Reset=True;User Id=ASPSession;password=ThePassword;Connection Lifetime=5" providerName="MySql.Data.MySqlClient" />
</connectionStrings>
<system.web>
<sessionState cookieName="Session" mode="Custom" cookieless="false" timeout="20" regenerateExpiredSessionId="true" customProvider="MySqlSessionStateProvider">
<providers>
<add name="MySqlSessionStateProvider" type="MySql.Web.SessionState.MySqlSessionStateStore, MySql.Web, Version=6.5.4.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d" applicationName="MySQL Test site" description="" connectionStringName="LocalMySqlServer" writeExceptionsToEventLog="False" autogenerateschema="True" />
</providers>
</sessionState>
</system.web>


Does anyone have any suggestions as to why this would cause such a bottleneck?

Thanks