3 ms·
I disagree. It was pretty good even back in 2005. There were a couple of very large high traffic sites I ran on it back then. I wouldn’t use it now because the
by hughrr 5y ago
I disagree. It was pretty good even back in 2005. There were a couple of very large high traffic sites I ran on it back then.
I wouldn’t use it now because the big cost is always humans in a project and anything .Net turns into a damage amplifier because of the amount of fettling and dealing with churn you have to do to get anything done. Even with .net 6.
- tomnipotent 5y agoAgreed. I had a web app in 2006 handling 20k RPS on three dual core/2GB servers without breaking a sweat. This included per-server connection pooling to MSSQL and lots of UDP traffic on top of memcached. It was rock solid.