OpenFreeMap survived 100k requests per second
blog.hyperknot.com
OpenFreeMap survived 100k requests per second
1–10 of 140 posts
Re: OpenFreeMap survived 100k requests per second
#2Thank you for this breakdown and for this level of transparency. We have been thinking of moving from MapTiler to OpenFreeMap for StatusGator's outage maps.
Re: OpenFreeMap survived 100k requests per second
#3The article mentions Cloudflare, so how much of this was cached by them?
Re: OpenFreeMap survived 100k requests per second
#4The article mentions Cloudflare, so how much of this was cached by them?
Do you even read the article?
Re: OpenFreeMap survived 100k requests per second
#5sounds like they survived 1,000 reqs/sec and the cloudflare CDN survived 99,000 reqs/sec
Re: OpenFreeMap survived 100k requests per second
#6Thank you for this breakdown and for this level of transparency. We have been thinking of moving from MapTiler to OpenFreeMap for StatusGator's outage maps.
Feel free to migrate. If you ever worry about High Availability, self-hosting is always an option. But I'm working hard on making the public instance as reliable as possible.
Re: OpenFreeMap survived 100k requests per second
#7> I believe what is happening is that those images are being drawn by some script-kiddies.
Oh absolutely not. I've seen so many autistic people literally just nolifing and also collaborating on huge arts on wplace. It is absolutely not just script kiddies.
> 3 billion requests / 2 million users is an average of 1,500 req/user. A normal user might make 10-20 requests when loading a map, so these are extremely high, scripted use cases.
I don't know about that either. Users don't just load a map, they look all around the place to search for and see a bunch of the art others have made. I don't know how many requests is typical for "exploring a map for hours on end" but I imagine a lot of people are doing just that.
I wouldn't completely discount automation but these usage patterns seem by far not impossible. Especially since wplace didn't expect sudden popularity so they may not have optimized their traffic patterns as much as they could have.
Re: OpenFreeMap survived 100k requests per second
#8Re: OpenFreeMap survived 100k requests per second
#9>Nice idea, interesting project, next time please contact me before.
It's impossible to predict that one's project may go viral.
>As a single user, you broke the service for everyone.
Or you did by not having a high enough fd limit. Blaming sites when using it too much when you advertise there is no limit is not cool. It's not like wplace themselves were maliciously hammering the API.
Re: OpenFreeMap survived 100k requests per second
#10So, OFM was hit by another Million Dollar Homepage for kids.