[postgis-users] Strange result about spatial indexes?

[Paul Ramsey]

FYI, here's the Shark profile for the fast case. It's like that expand
call is causing a great deal of caching that is not happening in the
bare SQL.



On Fri, Aug 14, 2009 at 10:18 AM, Paul Ramsey<pramsey at opengeo.org> wrote:
> Switching from storage = main (compression allowed) to storage =
> external (no compression please) in the create type declaration makes
> the standard query 5 times faster (489ms vs 2441ms), but still 5 times
> slower than the st_expanded case (96ms).
>
> Attached is the new shark profile.
>
> On Fri, Aug 14, 2009 at 10:06 AM, Paul Ramsey<pramsey at opengeo.org> wrote:
>> Ok... well the problem is pretty clear, see the Shark profile
>> attached. Now to figure the solution :)
>>
>> On Fri, Aug 14, 2009 at 9:58 AM, Paul Ramsey<pramsey at cleverelephant.ca> wrote:
>>> Got it, Safari didn't like it but FF did.
>>>
>>> On Fri, Aug 14, 2009 at 9:52 AM, Kevin Neufeld<kneufeld at refractions.net> wrote:
>>>> Paul Ramsey wrote:
>>>>>
>>>>> I am still waiting for a
>>>>> sample data set I can download, that link didn't work for me at all.
>>>>>
>>>>
>>>> The link works for me.  The website has a download link to the zip file.
>>>>
>>>> _______________________________________________
>>>> postgis-users mailing list
>>>> postgis-users at postgis.refractions.net
>>>> http://postgis.refractions.net/mailman/listinfo/postgis-users
>>>>
>>>
>>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: screenshot_03.png
Type: image/png
Size: 182860 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20090814/204504be/attachment.png>