search

kercos / geomodel

Automatically exported from code.google.com/p/geomodel
0 stars 0 forks source link

Proximity queries need better optimization #1

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Proximity queries currently can balloon out in query time if max_distance 
is unbounded.

Another point of optimization is in the first few geocells they look at.. 
for example, this is a trace of the first few cells looked at by a 
proximity query:

9a9c04895e7c9
9a9c04895e7c
9a9c04895e7
9a9c04895e
9a9c04895
9a9c0489
9a9c048
9a9c04
9a9c01

This can probably be optimized in some way.

Original issue reported on code.google.com by api.roman.public@gmail.com on 27 Apr 2009 at 6:39

GoogleCodeExporter commented 8 years ago

Original comment by api.roman.public@gmail.com on 26 Jul 2009 at 6:46

GoogleCodeExporter commented 8 years ago 
A very promising lead is http://code.google.com/p/asynctools/, which might make 
IN
queries parallelizable. This would boost performance for both proximity and 
bounding
box queries.

We should highly consider using asynctools!

Original comment by api.roman.public@gmail.com on 3 Sep 2009 at 4:04

GoogleCodeExporter commented 8 years ago 
Almost done in withasync branch:
http://code.google.com/p/geomodel/source/browse/#svn/branches/withasync

Original comment by api.roman.public@gmail.com on 6 Oct 2009 at 9:52

GoogleCodeExporter commented 8 years ago 
was this merged into trunk?

Original comment by ghi...@gmail.com on 18 Feb 2010 at 8:19

GoogleCodeExporter commented 8 years ago 
Nope, not merged yet. When I have some time to work on this, I'll merge into 
trunk. This 
should add a nice boost to performance.

Original comment by api.roman.public@gmail.com on 24 Feb 2010 at 2:18

GoogleCodeExporter commented 8 years ago 
Is the version in branches/withasync stable?  Very interested in trying it out 
...

Original comment by stephen....@gmail.com on 4 Mar 2010 at 10:15

GoogleCodeExporter commented 8 years ago 
It is stable, I just haven't had the time to merge it intro trunk and make a 
release out of it. Also still weighing 
options for packaging up asynctools into the source directly.

Original comment by api.roman.public@gmail.com on 8 Mar 2010 at 11:48

GoogleCodeExporter commented 8 years ago 
Looking forward to this release.

Original comment by aaron.je...@gmail.com on 5 Mar 2011 at 9:40

GoogleCodeExporter commented 8 years ago 
Can proximity queries be optimized sufficiently at all? With a cpm of $0.36 and 
1 request per second you burn $10000 a year. That's too much. Even if we could 
slash the query cost in half ist still a lot. Any thoughts?

Original comment by katz...@gmail.com on 1 May 2011 at 6:27

GoogleCodeExporter commented 8 years ago 
Any ETA on when/if this is likely to show up would be appreciated!

Original comment by j...@simplylisted.com on 25 Sep 2011 at 2:44

GoogleCodeExporter commented 8 years ago 
Please, merge withasync into trunk!

Original comment by flavioju...@gmail.com on 14 Oct 2011 at 4:36