136 reputation
14
bio website google.com/profiles/andyyatz
location United Kingdom
age 33
visits member for 3 years, 7 months
seen Apr 5 '13 at 12:29
Java & Perl programmer

Apr
7
awarded  Notable Question
Apr
5
comment Poor Performance when using Spatial Indexes in MySQL
Wow that's really good. Now I'm not sure what I was doing wrong in my own tests. One thing that might be causing an issue is the nature of my data sets compared to more traditional geospatial data sets. That said I'm just guessing and have no basis for this. It's brilliant to see that you don't need to force the index into memory to get the speed.
Nov
26
awarded  Popular Question
Feb
1
comment Poor Performance when using Spatial Indexes in MySQL
I think this could be closer to the issue. TBH its the R-index I want; the other spatial maths is a nice bonus since that would have to be done in the API layer under the old system. I did try a bit of tuning but increasing key buffers did not help (other buffers will not help here like table buffer since its a 1 table query on my personal server). What is odd is that MySQL hammers my machine into the ground when the queries are run (100% during query run). That said its doing a full table scan so maybe it isn't that strange
Feb
1
awarded  Supporter
Feb
1
comment Poor Performance when using Spatial Indexes in MySQL
Unfortunately 1 dimension is vastly less populated than another dimension. To put this into context the human genome has 24 unique chromosomes (22 pairs and the two sex chromosomes) along with a bags of data which has been assembled to different levels. Which means if you map elements to the basic use case that is only 24 unique identifiers in one dimension. The original hope was that the R-tree index would have been able to perform not only more performant overlapping range checks but also differentiate between these regions in a single query.
Jan
21
awarded  Student
Jan
21
asked Poor Performance when using Spatial Indexes in MySQL
Jan
21
awarded  Autobiographer