kevintodler

Hi Guust,
Here the the issue is not about adding the cities in the Geodirectory.
The issue is about Geodirectory taking up huge mysql memory resources when it is not needed.

Developers implemented Ajax location switcher on the homepage so as to make location selection easier as against Geotheme which used php buffer method.

Yes, Ajax did greatly improved accessibility of Geodirectory in terms of handling locations and memory consumption to a certain extent.

But there are still certain issues which are ignored:

1. I think it is not a very good way to load all cities on manage location page from editing point of view. Since it will take a long time to load and access even 30000 to 50000 cities.
Additionally it will take up excess memory for processing huge amount data for both server and client side browser.
I think developers should redesign Admin manage location page in multilocation addon using ajax technology but in scalable approach (i.e., a user should be able to select cities for editing based on region or country selected, thereby omitting unnecessary cities for editing).

2. For the most part location switcher has worked well in selecting locations using ajax technology.
But when Geodirectory is loaded with more than 130000 cities, it uses huge amount mysql memory usage when searching locations in real time.
It happens because when you start typing letter say for example “new york”, it will then make search for name against whole of cities available in the database and so CPU usage goes extremely high for that instance or that particular request.
Since geolocation is the main feature of Geo directory, it is necessary to create optimized solution for the problem.
Imagine a site receiving more than 500 requests at a time, the server will simply crash.

My suggestion towards improving Location switcher.

We can just simply use additional cities csv file alongwith Ajax to populate data on location switcher homepage.
All Ajax calls can be to this csv file instead of database.
It will cut down unwanted request to database mysql server.
It will save a huge hardware resources and money for Geodirectory members and also attract more customers to Geodirectory.

Please do not ignore this issues just because there is no need to add locations in advance. Because sooner or later, this issue will be raised
in the forum.
Also there are people who add millions of listings to their site before making their site live and so you can imagine the amount cities that will be added to database.

The other day manilla raised a issue whether or not they should concern about performance issues when locations become huge.

https://wpgeodirectory.com/support/topic/csv-location-import/#post-12108

It seems that there are many issues with location manager.
I just recently uploaded 30,000 US state cities and the site turned out to be the most slowest.
Location manager plugin consumes 90% memory of all the plugins combined.

When I try to access all cities in homepage, it starts to behave abnormal and throws “browser not responding” error.
My whole browser gets hanged for about 4 to 5 seconds.
It seems like Geotheme was better at handling 30000 cities without causing loading issues.

I hope you will resolve this error at the earliest.

Hello everyone,
I have just recently created a world state cities sql dump file which is ready to be imported in to your locations database table.
It is exactly created according to Geodirectory requirements.
It has 246 countries, 3799 regions and 137528 cities of the world.
cities have been chosen based on 1000+ limit population.

Locations Sql Dump file is for sale on themetailors.com but it is yet to be approved by moderators.

Don’t want to wait then please mail me at email removed. I may give attractive discounts to my first 10 customers.

None of the sources on internet can compete my data because they are much costlier and almost useless. You will end up wasting your $300 to $600 for no results.