[postgis-users] lwgeom wkb output slower in 1.0 RC1
ralph.mason at telogis.com
Tue Jan 18 01:09:23 PST 2005
I need to dig this out.
I did a bunch of mods around this that 'deparse' a lwgeom directly to a
wkb (and I don't know the current state of the code, but removed the
preparse that was happening before it was feed to the lwgeom parser and
I will have a hunt.
>On Mon, Jan 17, 2005 at 08:22:10PM +0100, Aleksander Bandelj wrote:
>>WKB output in 1.0 RC1 is several times slower than in 0.9. Problem seems
>>to be the function WKBFromLWGEOM (used in AsBinary), which first
>>serializes lwgeom to hex string and then parses the string instead of
>>writing out WKB directly. Are there any plans to optimize this for 1.0.0
>That's a known problem. Note that also slowing down are a couple
>of calls to make it OGC *strict* (force 2d and drop SRID).
>I think we should speed them up before 1.0.0
>For standing up against patentability of software,
> Thank You, Poland!
>Read the intervention: http://kwiki.ffii.org/ConsPolon041221En
>Send your thanks: thankyoupoland.info
>Read/do more: http://www.noepatents.org/
>postgis-users mailing list
>postgis-users at postgis.refractions.net
More information about the postgis-users