Hi have an ASP.Net application that allows multiple users to query against a
cube. I am using ADOMD.Net to make the queries.

Based on what I have read to be best practice, when an ASP page makes a
query I create the connection, make the query and then close the connection.
The connection string is always exactly the same so as to take advantage of
connection pooling.

The problem is that opening, querying and then closing results in slow
performance - about 3 seconds each time. If I keep the connection open in a
Session variable, subsequent queries take under 1/2 second.

Since connections are limited resources and I need my application to scale,
keeping connections in user Sessions is not desirable.

Can anyone offer some advice on how to get good performance with not
dedicating connections?

Thanks,
Bill