Last post Apr 02, 2010 01:40 PM by DigiMortal
Apr 02, 2010 01:12 PM|dvprez|LINK
I'm rewriting an old website from about 6 years ago and moving it to a rackspace cloud site. Right now there's no caching at all. It pulls information out of a sqlserver database and I'm wondering how much caching is too much. The information I've found
in books and online haven't really given me many guidelines to work within. They say if your data doesn't change a lot and is queried regularly, cache it. When I try to ask the people at rackspace about RAM they tell me, you'll never have to worry about
The site gets about 40,000 unique visitors/day and does ~100k pageviews/day
The site has different sections based on Location.
/states/ <- I just cached this section for 24 hours as there's only 50 datatables
/cities/ <- datatable for every city
And then it has information about a specific Business and it will pull all the matches within a 40 yard radius.
/ShowMatching/ <- there's about 42,000 different datatables here (probably the same for cities)
Any help would be appreciated.
Apr 02, 2010 01:38 PM|qwe123kids|LINK
Apr 02, 2010 01:40 PM|DigiMortal|LINK
Beofre you start with data caching consider
output caching. You may achieve killer results on performance when you use it. ASP.NET output cache is powerful enough to support a lot of output caching scenarios. You can event write complex caching logic using VaryByCustom parameter. If output cache
is on and it is not enough then it is point to see if you can cache data.