if you've been around on this mailing list a bit, you probably remember
the performance tests I did last year. As more and more performance
improvements have accumulated in my test758 branch, it was time to
re-run a similar test. So, here's a short summary on those recent
activities. I will probably write a more detailed blog post later.
Hardware was very similar to last year (32GB, Intel Xeon E3-1270V3),
with the exception of a bigger SSD, which now holds a full attic
database (480GB DC SSD). Still commodity hardware for 50-60€/month.
First test was focused on ridiculously simple queries
[out:json];node(63174280);out; (with node ids increasing), but a larger
number of them in parallel.
Due to changes in the dispatcher processing, we're now at 2000
queries/s, or some 172 mio. requests/day.
Of course, I don't want to advocate this kind of usage, but it's good to
know, we can keep up with a large number of very small requests you
would typically see with interactive maps.
Second test was a simulation of a full day in the life of
overpass-api.de. That's 534'497 real queries in total, processed with 7
parallel processes in 10.75 hours, without any waiting time, though. I
found the response time distribution quite interesting:
> Second test was a simulation of a full day in the life of
> overpass-api.de. That's 534'497 real queries in total, processed with 7
> parallel processes in 10.75 hours, without any waiting time, though. I
> found the response time distribution quite interesting:
As I noted here , you could run the same test to fit an actual 24
hours time frame (or least try to match it as closely as possible), and
see what the CPU utilization looks like.
Unlike the situation on the main instance with 85%+ CPU utilization for
most part of the day, about 2 cpu cores (or 25% cpu utilization) seemed
to be sufficient to run all queries, as well a minutely db update, an
hourly area creation delta run, and gzip compression on the web server.
In conclusion, there's some very good potential to make much better use
of available resources.