Jukka,
This is what I thought too, but as you said the table is very small and
should not cause problems even if it did not have indexes.
Retrieving the data from sql server by other apps is fast, no problems with
that.
I have found a post by Sjoerd here:
http://blog.geoserver.org/2008/11/10/146/ and was wondering whether this
still could be the case or not. The table I am trying to use has an index on
the primary key and also a spatial index.
Of course 5m points is nothing compared to something like 300k points in
polygons, though so far I seemed to be unable to make it perform better.
dom
From: Rahkonen Jukka [mailto:jukka.rahko...@mmmtike.fi]
Sent: Wednesday, November 10, 2010 2:08 PM
To: Dominik Mikiewicz; geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Poor performance with SqlServer data source
Hi,
Almost always the reason for slow response of a database driven system is in
poor indexes. However, your table is so small that it should be fast even
without indexes. Anyhow, check that you have a spatial index in place and
normal indexes for attributes which are used in queries. Try to capture the
SQL queries which are sent to the database and send them with plain SQL with
timing on. It is also possible that your client is slow, not Geoserver.
What client do you use? I prefer to use hand written WMS requests and web
browser for first tests, wget and jmeter when I want to capture some
comparable numbers about the speed.
-Jukka Rahkonen-
_____
Lähettäjä: Dominik Mikiewicz [mailto:dominikmikiew...@o2.pl]
Lähetetty: 10. marraskuuta 2010 14:47
Vastaanottaja: geoserver-users@lists.sourceforge.net
Aihe: [Geoserver-users] Poor performance with SqlServer data source
Hi list,
I am trying to set up an SQL Server data source for my geoserver. All goes
fine, I can connect to the server, pull the data and publish a layer.
The problems start when I try to view my layer in a browser. This is
terribly slow even though I have only roughly 8k polygons in a table.
A temporary solution is to use shp but the system will have to provide
means for updating the data on a daily basis and file based storage does not
seem to be the best thing
Any ideas on how to improve performance with sql server behind appreciated.
Thanks
Dominik
------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a
Billion" shares his insights and actions to help propel your
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
