• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Avoiding the /. effect

wacki

Senior member
I have a site on e-rice.net. If my website gets on /. is there a way to avoid it being DDOS. I know sites are mirrored on /. but I'd like to keep an accurate count of how many people see the website. THerefore I don't want my site to crash.
 
the only way is to beef up and then run load tests. Nothing makes a server guy sweat like 10K transactions a second on their servers.
 
10k transactions/second on a web server should not be a problem in 2006.

See http://www.kegel.com/c10k.html

Obviously, the more work you do to serve up a page and the more objects you put on a page, the more connections you need to be able to handle simultaneously. Ergo, highly-dynamic sites are not good for your connection rate, and/or require more thoughtful and more costly design.

wacki, "I'd like to keep an accurate count of how many people see the website."

That's not possible. Do some Google searching to find out how deep that rat hole goes. It's simply a trade off between how wrong you want your numbers to be and how much you're willing to spend to get your numbers. Unless this information is seriously revenue generating, I'd give up on it.
 
Originally posted by: cmetz
10k transactions/second on a web server should not be a problem in 2006.

See http://www.kegel.com/c10k.html

Obviously, the more work you do to serve up a page and the more objects you put on a page, the more connections you need to be able to handle simultaneously. Ergo, highly-dynamic sites are not good for your connection rate, and/or require more thoughtful and more costly design.

wacki, "I'd like to keep an accurate count of how many people see the website."

That's not possible. Do some Google searching to find out how deep that rat hole goes. It's simply a trade off between how wrong you want your numbers to be and how much you're willing to spend to get your numbers. Unless this information is seriously revenue generating, I'd give up on it.

We do a lot of testing on large sites, including lots of DB queries, and some web applications. It's not very hard to crash a web server (we do it all the time). We have 5 sites with 100Mb backbone connections, and dual OC3's from the office, most folks don't get that much bandwidth though.
 
Back
Top