I did a bit of digging in the source with some help from the uWSGI creator and found that this is a really easy fix. You can simply find/replace for GEOIP_MEMORY_CACHE/GEOIP_STANDARD in src/http/modules/ngx_http_geoip_module.c. Nginx compiles fine and GeoIP support works. RAM usage has returned to normal. I'm not an experienced dev but this should be easy to turn into a config option with a patby HittingSmoke - Ideas and Feature Requests
mod_geoip2 by default reads the GeoIP database from disk and only caches to RAM when it's explicitly configured to. Nginx only caches the GeoIP database to RAM, increasing the RAM usage many times over for each worker. For situations where GeoIP data is seldom used it would be extremely valuable to sacrifice some speed to save RAM by caching the database to disk instead of keeping it in RAM 24/7.by HittingSmoke - Ideas and Feature Requests
This is supported on mod_geoip for Apache to reduce memory usage. Is there a way to do this in Nginx so I can use the GeoIP city database without it taking up a ton of RAM?by HittingSmoke - How to...
I run three vhosts on my nginx 1.1.9 server. example.com sub1.example.com and sub2.example.com. Each one has the server name explicitly defined in it's vhost config file. There are no config entries for _ and nothing to fall back on. All domains that should be used are explicitly defined. sub2 is only spun up when required for specific purposes. I have nginx configured in a Debian/buntu style cby HittingSmoke - Other discussion
In the pitfalls it lists redundant index lines as bad. I have `index index.php index.html index.htm;` at the top of my http block in my primary config file. In my PHP-FPM location blocks though I also have `fastcgi_index index.php` Is the fastcgi_index parameter redundant? Should I remove it since index.php is listed under index in the http block?by HittingSmoke - How to...
I'm having issues with getting Nginx running after installing from source. I'm getting an error on run: " invalid number of arguments in "try_files" directive in /home/.../nginx/conf/sites-enabled/default:11" This line is the PHP execution protection outlined in the pitfalls page. My nginx.conf and my sites-available/default file is as follows: worker_processes 1;by HittingSmoke - Other discussion