[postgis-devel] [PostGIS] #1145: Some addresses are very slow to Geocode
PostGIS
trac at osgeo.org
Tue Aug 2 19:26:13 PDT 2011
#1145: Some addresses are very slow to Geocode
-----------------------------+----------------------------------------------
Reporter: mikepease | Owner: robe
Type: defect | Status: closed
Priority: high | Milestone: PostGIS 2.0.0
Component: tiger geocoder | Version: 1.5.X
Resolution: fixed | Keywords:
-----------------------------+----------------------------------------------
Changes (by robe):
* status: new => closed
* resolution: => fixed
Comment:
Mike I think this should be resolved at r7689 for the random sampling of
the above I tested with the above I'm getting under 150ms speeds with more
than Minnesota data loaded on fairly crappy drives.
I still need to cleanup the second tier check but left that as is because
it catches some things the first doesn't. When it falls in 2nd tier things
get really slow with some cases. To prevent second tier, set teh
max_results to 1 using
geocode(address,1)
At some point, I might change the default from 10 to 1 since I would
assume most people just want one result and best result within reasonable
amount of time.
I'm going to close this out, but feel free to reopen if you still have
speed issues.
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1145#comment:4>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.
More information about the postgis-devel
mailing list