Re: ASP.Net Caching Questions
- From: "KJ" <n_o_s_p_a__M@xxxxxxxx>
- Date: Tue, 29 May 2007 22:14:19 -0400
Hi Phil,
I don't have specific testing results, and I have no trouble conceding to
your assertion about Cache vs. database speed.
I'm only trying to get across the general idea that a stored procedure
executing in roughly 5-20 MS is sufficient for 100% of the ASP.NET
applications I have or am likely to encounter. Sending HTML across the wire
is not expected to happen instantaneously, as the speed of the network,
number of hops, etc, is always a limiting factor.
Is yours a real-time-dependent application where the consequences of waiting
a few extra MS are potentially disastrous or extremely problematic? Unless
it can be proven that a massive aspnet process is safe, reliable, and
manageable at the O/S level, and doesn't introduce any resource-based
performance concerns of its own.... (Maybe other folks with more knowledge
about aspnet internals will chime in on this thread and provide specifics?)
Now, for curiosity's sake, could you tell us why this particular application
has to be so fast, or is that proprietary info (etc)?
-KJ
"Phil Sandler" <psandler70@xxxxxxxxxxx> wrote in message
news:1180453586.028085.59410@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
On May 29, 9:20 am, KJ <n_o_s_p_a...@xxxxxxxx> wrote:
A serialization option (other than XML) you might consider is binary
serialization (saving an object as a stream of bytes to some medium,
such as a varbinary SQL Server column). Check out the topic "basic
serialization" in msdn.
As stated, the lookups have to be as fast as possible, so the idea is
to have all the information in memory so that the lookups are
instant. Loading the information from a file or sql column will not
perform nearly as well.
One thing I thought of: What if for some reason the aspnet or iis
process tanks and has to restart? What would happen to your
application (I imagine that such an application would require serious
ramp-up time to load all the data)?
Yes, there would be ramp up time. This is an expected and acceptable
condition, so long as the application performs well when it's running.
SQL Server is built to withstand
these kinds of events, and a properly designed and optimized SQL
database will perform comparably to using Cache.
With all due respect, what are you basing this on? Have you ever
tested this? Lookup up information in cache is many, many times
faster than querying a database for it.
I appreciate your taking the time to respond, but I need to find
answers to my specific questions before I start looking at alternate
solutions.
Thanks,
Phil
.
- Follow-Ups:
- Re: ASP.Net Caching Questions
- From: Phil Sandler
- Re: ASP.Net Caching Questions
- References:
- ASP.Net Caching Questions
- From: Phil Sandler
- Re: ASP.Net Caching Questions
- From: KJ
- Re: ASP.Net Caching Questions
- From: Phil Sandler
- Re: ASP.Net Caching Questions
- From: KJ
- Re: ASP.Net Caching Questions
- From: Phil Sandler
- ASP.Net Caching Questions
- Prev by Date: RE: Please Help me Optimize my Code
- Next by Date: Global Var
- Previous by thread: Re: ASP.Net Caching Questions
- Next by thread: Re: ASP.Net Caching Questions
- Index(es):
Relevant Pages
|