RE: ViewState vs. Database
- From: MCM <MCM@xxxxxxxxxxxxxxxx>
- Date: Wed, 16 Jul 2008 01:59:33 -0700
Well, I decided for the best possible user performance, I need to disable
ViewState as much as possible to keep the html smaller. The slowest part of
the network is the outbound data transfer to the client - much slower that
the gig traffic on the internal network. However, from a cost perspective,
building out a SQL cluster is more expensive than adding load balanced web
servers. So rather than making extra db calls, I'm going to try and cache
data on the webserver. This will of course mean a strain on RAM for the
webserver, but that seems like the best performance to cost ratio I can come
up with.
"Steven Cheng [MSFT]" wrote:
Hi MCM,.
How are you doing?
Have you got any further ideas on this or have you determined which
approach to use? If there is anything else need help, please feel free to
post here.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
From: stcheng@xxxxxxxxxxxxxxxxxxxx (Steven Cheng [MSFT])
Organization: Microsoft
Date: Fri, 11 Jul 2008 02:09:59 GMT
Subject: RE: ViewState vs. Database
to
Thanks for your reply MCM,
Not absolute. At least I would prefer that. However, for a specific
application, it much depends on the actual cost of each stage( web client
to server, webserver, server to database server..). And the best way is
do some profiling and get some idea of the actual cost or bottleneck anddo
optimize against the critical point.the
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
Delighting our customers is our #1 priority. We welcome your comments and
suggestions about how we can improve the support we provide to you. Please
feel free to let my manager know what you think of the level of service
provided. You can send feedback directly to my manager at:
msdnmg@xxxxxxxxxxxxxx
--------------------
From: =?Utf-8?B?TUNN?= <MCM@xxxxxxxxxxxxxxxx><lzALYqj4IHA.4056@xxxxxxxxxxxxxxxxxxxxxx>
References: <DB321895-A729-496F-B9B5-423029159B7B@xxxxxxxxxxxxx>
<26F3D2C0-3938-4A43-9AC5-25180A287D40@xxxxxxxxxxxxx>
<uEmi0kn4IHA.1340@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: ViewState vs. Database
Date: Thu, 10 Jul 2008 10:47:02 -0700
query/update
1. If database server is powerful enough to support frequent
processing or such operations are not quite frequent, I'll always do
impactimportantquery instead of caching the data. Since that can save webserver memory.
So from a performance perspective, saving webserver memory is more
that reducing the load on the db server?
2. If data is quite large and operations are so frequent that may
asdatabase server, I'll first consider caching data at server-side (such
in memory cache) rather than use page's viewstate.
This is an interesting idea. But this seems to contradict #1. So the
question is still where to I want to place the heaviest load - web or db
server?
- Follow-Ups:
- RE: ViewState vs. Database
- From: Steven Cheng [MSFT]
- RE: ViewState vs. Database
- References:
- RE: ViewState vs. Database
- From: Steven Cheng [MSFT]
- RE: ViewState vs. Database
- From: MCM
- RE: ViewState vs. Database
- From: Steven Cheng [MSFT]
- RE: ViewState vs. Database
- From: MCM
- RE: ViewState vs. Database
- From: Steven Cheng [MSFT]
- RE: ViewState vs. Database
- From: Steven Cheng [MSFT]
- RE: ViewState vs. Database
- Prev by Date: RE: ViewState vs. Database
- Next by Date: Cast from one generic IDictionary to another
- Previous by thread: RE: ViewState vs. Database
- Next by thread: RE: ViewState vs. Database
- Index(es):
Relevant Pages
|
Loading