Hello Lee,
I suppose caching isn't efficient for this type of searches. I can propose
a kind of trick.
if you index your docs in order by (STARTIP,ENDIP) tuple, it should make
intersection faster. However it's rather theoretical consideration than
practical one.
More real one is to encode ip rang
Hi Otis
The cache was modest 4096 with a hit rate of 0.23 after a 24hr period.
We doubled it and the hit rate went to 0.25. Our interpretation is ip is
pretty much a cache busting value ? and
cache size is not at play here.
the q param is just startIpNum:[* TO 180891652]AND endIpNum:[180891652 TO
Hi
We are doing a lat/lon look up query using ip address.
We have a 6.5 million document core of the following structure
start ip block
end ip block
location id
location_lat_lon
the field defs are
the query at the moment is simply a range query
q=startIpNum:[* TO 180891652]A
