I use the javascript tools in chrome browser to analyze the network request
and response latency between the client and the geoserver. I found that
after the client successful established a connection with the geoserver, it
waits there for a short time (a random number from 1ms to 200ms, the chrome
network analyzer labels the period as "blocking"). After the waiting, the
geoserver starts doing its jobs. My question is, how to minimize the latency
to at most 100ms?
thanks for your time and sorry for my horrible English.
On Sat, May 17, 2014 at 11:43 AM, CD <ic.chungdau.wang@anonymised.com> wrote:
Hello,
I use the javascript tools in chrome browser to analyze the network request
and response latency between the client and the geoserver. I found that
after the client successful established a connection with the geoserver, it
waits there for a short time (a random number from 1ms to 200ms, the chrome
network analyzer labels the period as "blocking"). After the waiting, the
geoserver starts doing its jobs. My question is, how to minimize the
latency
to at most 100ms?
Without knowing what requests you're making it's hard to tell, but, in all
likeliness, GeoServer is doing work in that time.
For example, if the request is a WMS
GetMap, it's spending that time reading the data and painting it over a
BufferedImage,
you start seeing data flowing back only when the painting is done and the
image starts to be encoded in PNG/JPEG
Cheers
Andrea
--
Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK
for more information.
Ing. Andrea Aime @geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549