Caching vs. State

R. Groves

unread,

Jan 10, 2002, 11:58:20 AM1/10/02

to

I'm working on a ASP.NET project that will traverse three firewalls to
return report data to the end user. The first hit will be expensive,
so on subsequent requests, I would like to improve performance by
caching or storing the data in state.

After some brief research, I've come up with the following options for
.NET:

1. Output caching - stored in mem
2. In-proc session state - stored in mem
3. State service (out-proc) - stored in mem externally
4. SQL State mgmt - stored in SQL Server
5. Viewstate - stored in page form
6. Dynamic - no caching or state

Which of these options should provide the best performance? Again, the
datasets would contain large, report-type data.

Deon Fourie

unread,

Jan 12, 2002, 8:04:54 PM1/12/02

to

Hi

I'd go for #1. Does the data change often? If so, you'd
need to add mechanisms (CacheDependencies) for updating
the cache. The cache is application wide, so different
sessions will use the cache, where the rest of the
solutions will be handled on a per session basis.

Hope this helps
Deon Fourie

>-----Original Message-----
>I'm working on a ASP.NET project that will traverse three
firewalls to
>return report data to the end user. The first hit will be
expensive,
>so on subsequent requests, I would like to improve
performance by
>caching or storing the data in state.
>
>After some brief research, I've come up with the
following options for

>..NET:

>
>1. Output caching - stored in mem
>2. In-proc session state - stored in mem
>3. State service (out-proc) - stored in mem externally
>4. SQL State mgmt - stored in SQL Server
>5. Viewstate - stored in page form
>6. Dynamic - no caching or state
>
>Which of these options should provide the best
performance? Again, the
>datasets would contain large, report-type data.

>.
>

Message has been deleted

R. Groves

unread,

Jan 25, 2002, 1:19:38 PM1/25/02

to

Output caching does okay, but my stress tests indicate in-process
state management works best for a simple scenerio. I've put up my
performance benchmarks for this application here:

http://www.grovesinternet.com/aspnet

The report contains results for various optimization features
including Output Caching, State Management, Data Caching, and Web
Services. I'll be adding more (Remoting, etc.) later.

Regards,
Rory Groves

Groves Internet Consulting, Inc.
http://www.grovesinternet.com

Philip Quinn <wise...@aspalliance.com> wrote in message news:<ur8X9V$mBHA.580@tkmsftngp02>...
> It seems like your going to be using a lot of data so I would go with
> option #1. I would take number 5 and 6 off the list as the pages could
> become huge.
>
> ------------------------------------
> Philip Quinn.
> wise...@aspalliance.com
> thisDevelopmentPage -
> http://www.aspalliance.com/wisemonk/
>
> *** Sent via Developersdex http://www.developersdex.com ***
> Don't just participate in USENET...get rewarded for it!

Scott Guthrie (MSFT)

unread,

Jan 25, 2002, 2:53:14 PM1/25/02

to

What does the code you are writing look like? It would be great if you
could include it as well -- since interpretting numbers is pretty hard
without it.

Thanks,

Scott

"R. Groves" <r.gr...@usa.net> wrote in message
news:914e97ae.02012...@posting.google.com...

R. Groves

unread,

Jan 26, 2002, 1:26:06 AM1/26/02

to

I can't post all the code (corporate security reasons), but I will try
to add the ASPX page and key code-behind functions.

"Scott Guthrie $MSFT$" <sco...@microsoft.com> wrote in message news:<eDgzrndpBHA.1600@tkmsftngp07>...