freegeoip blog

index


Built-in map and multiple servers

05 Sep 2013 · @fiorix

Due to recent issues with redis management I decided to experiment with a built-in map for managing quota. It’s a Go map that uses the source IP of the connection as the key, and its value is the number of hits on the API.

The map implementation has reduced request processing times from an average of 800μs down to 300μs in production. However, there’s the disadvantage of resetting all quotas to zero when the server is restarted.

There’s one more optimization that I’d like to implement, which is what was used in one of the latest Python versions of freegeoip: convert the IP to int32 and use that as the map key to save some memory. The IP is being converted already for the SQLite query anyway, and is just a matter of reorganizing the code. Edit: Done.

For now, redis is optional and can be enabled or disabled any time in the configuration file.

Another new feature that has been added to the server is the ability to listen on multiple HTTP and HTTPS servers on either tcp or unix socket. Now the configuration file supports multiple <Listen> tags, each with individual settings for logging and use of xheaders.

If a <Listen> tag has a pair of <CertFile> and <KeyFile> tags then HTTPS is enabled.


freegeoip.net · source code