ASP. NET cache mechanism: balance between development efficiency and Optimization

No ASP. NET cache mechanism is used

The last time I talked about the performance of Memcached, it is true that the cache is not omnipotent, but it is absolutely impossible to have no cache? This is really the case. plentyofFish is doing this. It is also one of the few websites on the Internet that use the WISC (Windows + IIS + SQL server + C #) architecture. MS cannot talk about MySpace all the time, now, of course, we will not miss this opportunity to publicize it, But the irony is that people don't use the server controls that "look beautiful" at all, rather than using them. net technology is not as good as borrowing this platform. most of their page outputs are constructed strings or Response. write is simple, and they strictly abide by this rule when writing a program. In turn, think about the control of inheritance relationships of up to seven layers in the CommunityServer, it looks a bit like this: (basic) (webpage) (template-based) (Basic album template-based) (album replaceable style) the XXX control, look at this long attribute, implements different features in each layer of inheritance. The structure is actually quite clear. What is POF like? If the performance of the Audi is poor, it is troublesome. Those B4 Discuz! Should NT friends reflect on it :)

In other words, this does not mean that the Control of the pile of Microsoft parts is useless, but for Small and Medium-sized applications, what we need more is the development efficiency. Besides, the load is not that large, there is a suspicion of over-optimization. The most suitable thing is the best. It is the most important thing to get satisfied with users quickly.

In addition to the ASP. NET cache mechanism

Let's take a look at some interesting places in it:

1. Tens of millions of photo requests are processed by their servers, but they are all cached in memory and smaller than 2 kb.

3. Although Gzip technology increases the CPU overhead by 30%, it is worthwhile to save bandwidth.

4. Asp. Net cache mechanism is not used, because the data is updated too quickly and expires once it enters the cache.

5. A large number of simple statements such as if, else, And while + Response. Write are used to implement functions.

6. No one seems to have to use Server Load balancer)

Tens of millions of page views per day. The Server has only two webservers and three DB servers, and the optimization effort is really good.

The above is a further discussion of the ASP. NET cache mechanism: development efficiency and performance optimization should find an appropriate balance.

This article is from sharga's blog: distributed cache under. Net (3) -- what if we don't have a cache?

1. . NET distributed cache for Memcached execution speed detection
2. How to Avoid ASP. NET cache occupying system resources
3. . NET Cache Mechanism discussion and Comparison
4. Overview ASP. NET Cache Mechanism
5. Introduction to data caching in ASP. NET data cache