Distributed cache under. Net (3)-What if we don't have a cache?

.
Net distributed cache-from discuz! About the Cache Design of NT
Distributed cache under. Net (2)-a means to achieve distributed cache Synchronization

Distributed cache under. Net (3) -- what if we don't have a cache?

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, simple is beautiful, they are writingProgramIn this case, we strictly abide by this rule. In turn, we can think of the control with up to 7 layers of inheritance relationships in the communityserver. It looks a bit like this: (basic) (webpage) (template-based) (Basic album template-based) (album replaceable style) xxx control, look at this long string of attribute, it implements different features in each layer of inheritance, and its structure is quite clear. What is POF like? The performance of a hand-built Audi is just a little tricky. 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.

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. Server Load balancer (no one seems to have to use it)

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.

For other details, refer to this post.