We are using geolocation on our website - we are using IP of the visitor to locate the timezone of the visitor and then we display content based on the timezone.
We are using a geolocation mysql table with 3M rows for this.
The site is working fine when we receive maybe up to 100 visitors per second, but when that goes up to say 200 the server cannot process the query fast enough and the whole server stops. Old processes are backing up and new ones are coming in faster than old ones can be processed.
I had a developer add this functionality and he is no geolocation expert. He added the table and used a basic query. By what I've had a chance to read online this is a common performance problem for everyone dealing with geolocation on a basic level. Since he has no experience on how to better tune this query to be faster, we need a geolocation expert that can check it out and see what can be done.