![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have an ASP.NET application that accesses a AS 2k Cube with adomd. I do alot of calls to the cube via adomd to find it's meta-data. In every page that connects to the cube the connection is closed as soon as possible. This solution has worked well with resonable speed. I have now converted my application to use adomd.net and now my application runs slower than before. The main difference is that the first call to the cube (using the Cubedef object) take much longer time with Adomd.net. After the first call the following calls are fast. Since I close the connection after each page request I get this delay every time which results in poor performance. I have tried to store the open connection in the session and now the performance is very good. The downside of this approach is, besides a lot of open connections to the server, that aspnet_wp consumes alot of memory. 3 concurrent users results in a memory usage of 200~300 MB. I want to be able to serve at least 10 simultaneous users so this solution doesn't scale very well. I am using ADOMD.NET 8.0 and connect through IXMLA with this connection string: Data Source=SERVER;initial catalog=DATABASE;ConnectTo=8.0;Integrated Security=SSPI;Client Cache Size=10;Execution Location=3;Default Isolation Mode=1; The cube has a lot of roles defined so I run the application with Impersonate=true I prefer not to store the connection in the session so is there any way to minimize the delay for the first call to the cube? Or is there a way to make the memory usage smaller when storing the connection in the session? /Dinnan |
#3
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |