SessionState = SQL performance

[Jorge]

I'm moving session state to "sql mode" but I've some problems with performance in asp.net.

When using "inproc mode" the ReportViewer shows the report after 2.8 secs, while in "sql mode" it takes more de 30 secs. Is this normal?
My report has only one page with some images.

Thanks!

[Chavdar]

Hello Jorge,

It is quite normal to have a performance penalty when switching from InProc to an OutProc Session state. When objects are in the same process they are accessed almost instantly while when they are in another process/storage the data is marshaled back and forth using complex calls. Sometimes depending on the size and complexity of data the time may increase significantly. More information about the different session state modes and their performance you can find in the following links:

• ASP.NET Session State
• SQLServer vs StateServer for ASP.NET Session State Performance

One tip for improving performance when using Telerik Reporting in an out-proc session state is to feed it with data by using the Reporting Data Source components.

You can also read the Design Considerations for Out-Proc Session State KB article.

Kind regards,
Chavdar
the Telerik team

[Jorge]

OK. I've worked in a solution that solves the SQL-Session + Telerik problem.

PROBLEM
The original situation is this: Telerik Reporting generates a 15+ Mb object (for my report) that is stored in the asp.net session object. Each time I refresh the page, a new 15 Mb object is created, so if i refresh the page 4 times in a few seconds, for example, the session object grows to 60 Mb.
This causes a BIG performance problem: the first report load in 10 segs, the second in 20 segs... and so on. This is not a Telerik bug: it's the awful ASP.NET SQL-Server default implementation. Asp.net LOADS EVERYTHING from the database, and SAVES EVERYTHING when the page generation is done. While this is faster for handling small variables in the session object, it's useless if you are Telerik Reporting, of other components.

SOLUTION
Implement a custom session provider, that has a lazy loader so it only loads the necessary variables from session.
Using this solution I reduced loading time to 5 seconds each time the page loads (solving the refresh problem). Also It implements a "save only modified objects" mechanism, to reduce time, bandwidth, etc.
If anyone is interested in this solutions I'll post some code.

Cheers!

[Moe Islam]

Jorge:

I am also having some issues with SQL State, my report viewer hangs and do not display any report, kindly post you custom session handle for  my help!

Regards
Moe

[Jorge]

First of all: did you follow the Design Considerations for Out-Proc Session State  ? Specially using parameterless constructors and the "NeedDataSource" event?