Hi,
... and today, I've done some fiddling with the one of the GeoTools
postgis classes to make GeoServer really perform when used with PostGIS
and GEOS. In one test, which had taken 31179 ms to parse, query and
respond under yesterday's 1.0.1 release with GEOS and even longer
without, it now takes a total of 374 ms....
I'm testing against a table with half a million records, and spatial
queries are always under a second. I'm impressed. GeoServer rocks.
I'm not a GeoServer developer, so I've sent the (minor) changes to
Chris.
BTW: Have a look at a cool little demo site that allows on-line heads-up
digitizing, using GeoServer's transactional update capabilities.
http://www.moximedia.com:8080/imf-ows/imf.jsp?site=edit
Regards,
Doug
--
Doug Cates
Moxi Media Inc.
757 - 1641 Lonsdale Avenue
North Vancouver, BC, Canada V7M 2J5
Phone: 604-984-8109
Fax: 604-608-4764
E-mail: doug@anonymised.com
Web: www.moximedia.com
Thanks a ton for these fixes Doug. I'll roll them into the next release.
We may do a 1.0.2 release, but likely we'll just charge ahead with 1.1,
and get these in there. If anyone wants this before then, let me know,
and I can easily roll you a jar that'll be much faster with GEIS, thanks
to this work.
Chris
On 1 Nov 2003, Doug Cates wrote:
Hi,
... and today, I've done some fiddling with the one of the GeoTools
postgis classes to make GeoServer really perform when used with PostGIS
and GEOS. In one test, which had taken 31179 ms to parse, query and
respond under yesterday's 1.0.1 release with GEOS and even longer
without, it now takes a total of 374 ms....
I'm testing against a table with half a million records, and spatial
queries are always under a second. I'm impressed. GeoServer rocks.
I'm not a GeoServer developer, so I've sent the (minor) changes to
Chris.
BTW: Have a look at a cool little demo site that allows on-line heads-up
digitizing, using GeoServer's transactional update capabilities.
http://www.moximedia.com:8080/imf-ows/imf.jsp?site=edit
Regards,
Doug
--