[postgis-tickets] [PostGIS] #2260: Benchmarking speed between built-in tiger normalizer and pagc_address_parser

[PostGIS]

#2260: Benchmarking speed between built-in tiger normalizer and
pagc_address_parser
----------------------------------+-----------------------------------------
  Reporter:  robe                 |       Owner:  robe         
      Type:  task                 |      Status:  closed       
  Priority:  medium               |   Milestone:  PostGIS 2.1.0
 Component:  pagc_address_parser  |     Version:  trunk        
Resolution:  fixed                |    Keywords:               
----------------------------------+-----------------------------------------

Comment(by robe):

 I think I know what is wrong.  I think I'm still not taking advantage of
 your cache since your cache is a per query cache.  I was thinking since
 your function is a subcall of mine, it would be considered part of the
 same call, but I realize now each one is probably being treated as a
 separate call still even though its now part of a larger query.  Not sure
 how to get out of that.  I'll open a separate ticket for that as its not
 really your problem and an issue of how I'm wrapping it.

 Of course if you could somehow change this to a per prcoess backend cache
 rather than per query cache, that would solve the million calls per
 webservice issue as well as my problem :)

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/2260#comment:32>
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.