Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

geoip GEOIP_MEMORY_CACHE vs GEOIP_STANDARD #25

Closed
abgit opened this issue Aug 29, 2013 · 3 comments
Closed

geoip GEOIP_MEMORY_CACHE vs GEOIP_STANDARD #25

abgit opened this issue Aug 29, 2013 · 3 comments

Comments

@abgit
Copy link
Contributor

abgit commented Aug 29, 2013

Hi,
On latest unstable branch commit, GeoIP_new was changed from GeoIP_new(GEOIP_MEMORY_CACHE) to GeoIP_new(GEOIP_STANDARD).

Note that, GEOIP_MEMORY_CACHE is much much faster than GEOIP_STANDARD.
On my 2 million hits file, i get this parsing times:

  • GEOIP_STANDARD: in 40 seconds
  • GEOIP_MEMORY_CACHE: in 12 seconds

almost 4x faster.

best,

@allinurl
Copy link
Owner

@abgit Thanks for the heads up on this. On 2 million hits, how big is the difference in terms of memory consumption between GEOIP_MEMORY_CACHE and GEOIP_STANDARD?

@abgit
Copy link
Contributor Author

abgit commented Aug 29, 2013

After a top analysis, i really don't see a major difference.

  • GEOIP_STANDARD: in 40 seconds, top-mem-virtual 12000, top-cpu 95%
  • GEOIP_MEMORY_CACHE: in 12 seconds, top-mem-virtual 13000, top-cpu 65%

GEOIP_MEMORY_CACHE is much faster and with lower cpu :)

best,

@allinurl
Copy link
Owner

Added GeoIP database flag, defaults to GEOIP_MEMORY_CACHE. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants