Re: Connection pooling
От | John R Pierce |
---|---|
Тема | Re: Connection pooling |
Дата | |
Msg-id | 5272BC72.8080403@hogranch.com обсуждение исходный текст |
Ответ на | Re: Connection pooling (andy <andy@squeakycode.net>) |
Ответы |
Re: Connection pooling
|
Список | pgsql-general |
On 10/31/2013 1:09 PM, andy wrote: > I'm not sure if geoserver is like openLayers/mapserver, but in the > later case (which I use), you can set it up to have the browser > (running openLayers) request multiple layers at the same time... and > on top of that each layer can be requested in tiles. (That way when > you drag the map it only has to load new tiles, and not the entire > image, which makes the animations smooth) > > Anyway, one webclient * 5 layers * tiles = lot and lots and lots of > web requests (which, would make lots of db hits). sure, but those hits shouldn't each be using a new connection, no more than 2-4 of them should be processed concurrently following http 1.1 guidelines, so no more than 2-4 connections should be required. the behavior the OP descibed sounded like the tomcat applets aren't closing their connections, thats broken behavior. -- john r pierce 37N 122W somewhere on the middle of the left coast
В списке pgsql-general по дате отправления: