[OpenLayers-Users] Re: Updating Data: Comet, Push, or What?

[Michael]

I have not done any measurements.

The advice on server load is entirely based on commentary on various 
websites.  I suppose, as I set this thing up, a test is a good idea.

The likely use case here is that there will be a few thousand users at 
any one time who will need updates every five minutes or so.  According 
to what I have read, if I use a technique that holds a normal Apache 
server connection open for each of those connections it will bog the 
server down badly.

In fact, for the basic data upload, I am using the techniques you 
describe.  This is a matter of good design when more than one visitor is 
expected!  The concern I have is multiple long-polling AJAX calls.


Research continues....

MM



On 5/21/2011 12:52 PM, Arnie Shore wrote:
> Have you done any measurements that tell you where the server-side 
> time is going?
>
> If it's database access - and you're satisfied that your schema design 
> is optimal - then solutions to that problem include some variations on 
> the following.
>
> a.  A caching mechanism that would update the cache at a rate you 
> select, rather than at the rate of visits.
>
> b.  Create a static page that often, and respond to users with that 
> static page.
>
> Client-side, if memory is being consumed and not returned, then 
> forcing a page reload can clear that issue.
>
> AS
>
>
> On 5/21/2011 3:01 AM, Kris Geusebroek wrote:
>> Hi all,
>>
>> A timer event would certainly work. Although i found that with Internet
>> Explorer the memory consumption is huge. Every update will create new
>> dom elements and the removal of dom elements is not freeing the memory
>> out of the box.
>> So whatever solution you choose you should take that in mind
>>
>> Cheers Kris
> _______________________________________________
> Users mailing list
> Users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/openlayers-users