Hey Eliecer,
I'm little confused to what your exact test was. First you talk about search then about "show all tabs on map".
About the search: In version 3 and 3.1 the search is not restricting the length of the returned results. In the latest dev. build I've changed the way the search works.
Now it is searching in your current view and the list of returned results is restricted to the number selected in the options. I also count how many hotspots matching the search criteria there are in total on the map and if in the current view we have 0, then I tell the user that "there are 0 results in your current view, but there are more hotspots if you zoom out".
Now this could be improved by -> if the current view has 0 results, make another search and augment the current bounds by 1km, 10km, 100km etc. till we have some results and then we can automatically zoom out the user... This will be something for 3.3
Since now the returned list with hotspots is restricted -> the search should be way faster. If you actually compare the demo to the dev site and search for "lipsum" you'll actually see that on the demo site -> the search works properly, on the dev site -> it doesn't return any results in the menu because the server runs out of memory for the 90k locations in the db.
demo.compojoom.com/hotspots#!/search=lorem
demo.compojoom.com/dev/index.php/hotspots#!/search=lorem
About "show all tabs on the map":
As I wrote this in the documentation - if you set the list length to 100 and you have 10 categories (each category has let us say 500hotpsots) and all 10 category tabs are open, then when you move around we need to make a query that will return 1000 locations. The biggest problem here is bandwidth. If you look carefully you'll see that the custom tiles are shown first, and then after some time the real markers are displayed.
That is because - the total tile size is around 20kb. Where the request for the markers is around 400kb!
If you have a lot of locations the only way to make the map faster is by reducing the number of markers shown at once. This is why google, mapquest and some other function as they do. They show you - 10 main markers -> everything else is custom tiles. When you move to a custom tile -> they make an ajax request in the background and create the markers with the returned information.
Another example -> if you are zoomed out on the demo map with the parks category there are 90k locations. The map is divided in 6 visible tiles. Each tile has been restricted to show max. 500 places. The size of the png. is 6kb. When you move with the mouse on a tile -> I do a backend ajax request that returns the locations -> the size of the ajax request is 70kb and takes around 400ms to execute. And this is actually a lot of time. I actually think that I should reduce the max number of locations per tile to 200. If you are zoomed out, there is no point in showing you so many locations - one has to zoom in to see more information.
Anyway - my point is - the search in the new dev. version should be way faster.
"Show all tabs on map" is impossible to be fast if you have set the marker list limit to a high number and you have a lot of open tabs.
Cheers,
Daniel
