Hi,
playing with KML I noticed a suboptimal behaviour.
Open the KML link for states, make sure USA is in the view, then
kick the globe so that it starts spinning slowly (drag and release
while still moving the mouse).
During the spin, GeoServer will use CPU like crazy, I suppose because
GE is asking for the same KML again and again. Is there any way to
reduce the number of calls some way?
A few users with a globe that's spinning can easily take GS to his
knees this way...
Cheers
Andrea
Andrea Aime ha scritto:
Hi,
playing with KML I noticed a suboptimal behaviour.
Open the KML link for states, make sure USA is in the view, then
kick the globe so that it starts spinning slowly (drag and release
while still moving the mouse).
During the spin, GeoServer will use CPU like crazy, I suppose because
GE is asking for the same KML again and again. Is there any way to
reduce the number of calls some way?
A few users with a globe that's spinning can easily take GS to his
knees this way...
Mbah, wrong assumptions.... it's GE that's sucking all the cpu while
the globe is spinning, not GeoServer.
Sorry for the silly question.
Cheers
Andrea
Well, that's not entirely true, at least in my experience on some versions of Google Earth. I think Tyler reported on this awhile back - if the dataset is not shown at all Google Earth will sometimes fire a request every time the globe moves until the dataset is back in view. I reported the problem, not sure if it's been fixed. Though maybe that's not what you're experiencing... But I found no way to fix it on our side.
Chris
Andrea Aime wrote:
Andrea Aime ha scritto:
Hi,
playing with KML I noticed a suboptimal behaviour.
Open the KML link for states, make sure USA is in the view, then
kick the globe so that it starts spinning slowly (drag and release
while still moving the mouse).
During the spin, GeoServer will use CPU like crazy, I suppose because
GE is asking for the same KML again and again. Is there any way to
reduce the number of calls some way?
A few users with a globe that's spinning can easily take GS to his
knees this way...
Mbah, wrong assumptions.... it's GE that's sucking all the cpu while
the globe is spinning, not GeoServer.
Sorry for the silly question.
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:4005,46c07c5b250661431913854!