5 ms·
Ok I am confused, 60k hits in a day? What broght down the website? 72MB of size, network congestion, or 60k hits? Even with authentication for download what can
by maxpert 9y ago
Ok I am confused, 60k hits in a day? What broght down the website? 72MB of size, network congestion, or 60k hits? Even with authentication for download what can bring the system down? I have handled more traffic on a RPi with 100MBps connection. I really don’t get it.
- lstyls 9y agoIf you're hitting a single box, this seems perfectly possible - especially if the server or the network is poorly configured. This is what CDNs are for.
- dsfyu404ed 9y agoThis isn't Joe's blog running from a desktop found in a dumpster. It's a university with actual infrastructure. They should be able to handle this. Registration is probably more load. A 72MB file being served 500,000 times over a 24hr period is 3-4Gb/sec. The department probably has one or more web servers serving content off a network drive. Your average "rack of network storage" won't even blink at that. There was probably a gigabit switch somewhere or that was being a bottleneck or the web server was simply misconfigured for this task.
- lstyls 9y ago+1, thanks for the correction. Apparently I have a skewed perspective only working on web at big corporate joints.
- maxpert 9y agoHere I made a quick copy and a quick domain, almost 10 LoC and it will be more reliable than what Cambridge had http://hawking.sibte.ml/ http://hawking.sibte.ml/
- chauhankiran 9y agoWow! Thanks. But, I do not understand the <script> tag in homepage contains lots of ![]+[].
- alain_gilbert 9y agoI think it's just a way to document.write his email address, so no bot/crawler can directly see it. Edit: It evaluate to `document.write('HIS_EMAIL at gmail')`
- pennaMan 9y agoIf the browser can do it what's stoping a headless browser bot from evaluating it all the same? Is it just to lower the attack surface?
- poooogles 9y ago>If the browser can do it what's stoping a headless browser bot from evaluating it all the same? The vast majority of crawlers aren't that smart, headless browsers used to be painfully slow so no one used them.
- contravariant 9y agoEvaluating all javascript to see if it eventually writes an email address is not a good idea. In fact doing so probably violates the halting problem somehow.
- fnwx17 9y agoLove the irony on that! Which makes me wonder how much valuable content and research in locked away on technologically ancient servers in Cambridge and Oxford.
- qurashee 9y agoMore modern and up to date than you'd think :) Some departments here in Oxford have a server life-cycle of 3-5 years. It's just that nobody bothers for higher than expected volume of traffic unfortunately (a practice that can be extrapolated to many things in academia).
- mayank 9y agoProbably a burst of traffic hitting a single box web server, rather than 60k hits spread out evenly over a day.
- posterboy 9y agoWith a half time of 3 days of interest and a 100 MBps connection the average download time would be 3 hours. That would indeed seem unusual for today. but 30k page hits spaced out over 60 hours is not too much of a burden on top of that.
- yreg 9y agoIt hit top of reddit yesterday, I don't think it was a mere 60k hits.
- mortehu 9y ago(60000 connections * 72 MB) / (24 hours * 40 Mbps) ~= 10 concurrent connections. If your server is configured for a low number of concurrent connections, it can easily seem swamped if a small number of people are concurrently downloading a large file slowly. All that's happening is that it's not accept()ing new connections until existing ones finish.
- gilleain 9y agoHeh, I don't know what the current hardware is for the CUDL DSpace repository, but having helped upgrade it a few years ago, I can't say the software is the fastest. It's a java application with XLST in the page rendering pipeline, so not exactly optimised for speed.
- masonic 9y agoWhat brought down the website? The Greys.