there is actually a djbdns-based dns-auth server called geoipdns that has some more functionality and adds views with per-record granularity instead of per-zone for geo-based filters/rules: http://pub.mud.ro/wiki/Geoipdns

I do not have formal benchmarks at hands, but I have myself experienced a significant performance improvement on the server. Very important point that is quite often omitted in the benchmarks is that although nginx may be for example 10% faster in serving requests, CPU and memory usage are much, much less, actually almost zero. This leaves it all for PHP/MySQL and other memory/cpu hungry processes. My server load averages have dropped significantly after I moved to nginx and its flexibility in for example adjusting config files or even upgrading the web server without stopping service for a second are unbeatable.

Can you show any benchmarks which would show significantly better performance for nginx compared to lighttpd ?

I’ve seen nginx being say 10% faster for example but that is minor. I’ve also see people comparing things wrong, ie you need to configure multiple workers in lighttpd 1.4 to serve many small files from disk efficiently etc.

The choice for lighttpd in this case was made because there is good documentation for developing modules, together with good enough performance.

It just wasn’t written that way (and I would agree that it is bad). Partitioning on “at rest” data makes sense or on data that doesn’t require 24/7. For 24/7… I suspect someone is going to have to come up with a solution that doesn’t require blocking.

I need to look and see if NDB can now do online partitioning adding, I know it was talked about.

Cheers,
-Brian

Right now only Archive does a lazy open (and I am thinking about adding a reaper to go through and close based on non-usage).

One thing to consider for those talking about events. An event that does an alter will lock the table up throughout the alter. You also need 2X the diskspace during the alter (half for the old partition, and half for the new).

Cheers,
-Brian

So there is nothing totally unexpected. Though I would expect lazy opening would make a lot of sense for partitioning so table is only opened first time it is accessed. There are many cases, like joins when static partition pruning does not work but by join conditions only few partitions will be touched.

Surely you can use event scheduler or cron job to do the stuff. It is just another piece to maintain independent of table with partitions itself. Especially as in this case there are multiple partitioned tables on the server and their number can change at the same time. Surely you can still do it it is just more complicated than some auto creation would be.