3 ms·
For those hitting errors, the code is on GitHub [0] And here's my own results: [1] EDIT: I've also mirrored the repo, and turned it into a site using GitLab C
by shakna 10y ago
For those hitting errors, the code is on GitHub [0]
And here's my own results: [1]
EDIT: I've also mirrored the repo, and turned it into a site using GitLab CI: [2]
[0] https://github.com/allanlw/cache_size https://github.com/allanlw/cache_size
[1] http://i.imgur.com/LKIvyCt.png http://i.imgur.com/LKIvyCt.png
[2] http://shakna-israel.gitlab.io/cache_size/cache_size.html http://shakna-israel.gitlab.io/cache_size/cache_size.html
- awirth 10y agoThank you! My VPS got overloaded and I put it behind a CDN but I don't know where the DNS SERVFAILs came from.
- shakna 10y agoNo idea. Putting stuff on HN is a great way to watch it all break. Happy to help.
- awirth 10y agoBefore my VPS folded it was mostly bot traffic, which I hadn't been expecting. Evidently many follow the HN RSS feeds and hit new posts (repeatedly..) when they show up.
- robertelder 10y agoI've also noticed something in my logs that is stupidly requesting these 'apple-touch.png' icons over and over thousands of times. It seems to discover links from HN. Even if you create a file with that name, it will just keep requesting it over and over.
- shakna 10y agoiOS seems to be the only thing that uses that particular favicon. Lots of iPhone users? Or all from the same address? Cos that'd be odd.
- Klathmon 10y agoI saw something like this once where a shitty app was using some of the iPhone icons, but it was proxying them all without any caching. So if 10 people would load the app, their backend would make 10 requests to the icon on my server and then would relay those images to each user. I could see something like this happening with a "push" system so when something new is posted on HN some overly clever dev decided to push the icon and title to each device to be read later but forgot to cache the icon so they end up slamming the server.
- vignesh_m 10y agoAre there distinct lines at 32k, 256k, 4M because of different levels of caches? I feel like 32k is the L1 cache and so on.
- shakna 10y agoOn a less powerful machine, I got 32k, 1M, and 8M. Just where the caching is happening inside the JS engine would be interesting but probably take me weeks to dig down. Any ideas?