[horde] High load with enabled activesync - Horde 5.1.2

[Michael J Rubinsky]

Quoting Sascha Schmidt <sascha at schmidt.ps>:

> Zitat von Sascha Schmidt <sascha at schmidt.ps>:
>
>> Zitat von Arjen de Korte <arjen+horde at de-korte.org>:
>>
>>> What is the value of $conf[activesync][ping][waitinterval]? Looking at
>>> the above log, it looks like it is not set. This could be the reason why
>>> it is now continuously looking for changes. That's definitly not what
>>> you want. Try setting it to something like 60 seconds or so.
>>
>> After changing the configuration values to:
>> conf['activesync']['enabled'] = true;
>> $conf['activesync']['emailsync'] = true;
>> $conf['activesync']['version'] = '14.1';
>> $conf['activesync']['logging']['path'] = '/var/log/horde';
>> $conf['activesync']['logging']['type'] = 'custom';
>> $conf['activesync']['ping']['forcedheartbeat'] = 60;
>> $conf['activesync']['ping']['deviceping'] = false;
>> $conf['activesync']['ping']['waitinterval'] = 60;


The "heartbeat interval" is the amount of time that the PING or  
Looping SYNC will maintain an open connection. If no changes are  
detected before this time expires, a response is sent to the client  
and the connection terminates (the client then usually issues another  
request).

The "waitinterval" is the number of seconds to wait between checking  
the backend systems for changes.

You have set a forced heartbeat of 60 (almost certainly not really  
what you want), and a waitinterval of 60. This means that the  
heartbeat will most likely expire before the end of the waitinterval.

If you *really* want to force a hearbeat time (and such a short one at  
that), then your waitinterval should be much smaller.

The most efficient thing to do is to let the client manage the  
heartbeat interval. Most clients have a smart algorithm that changes  
the interval, and frequency of retries in the case of errors etc...  
depending on things like network conditions. The shorter the heartbeat  
interval, the quicker the battery on mobile devices will drain since  
it takes much more energy to initiate the connection then it does to  
maintain an open connection. This is why, by default, most clients  
will attempt a heartbeat closer to 60 minutes, if not longer.


>> The behaviour has changed. Now I've got pings/updates/polls every 10
>> seconds. But 10 seconds is not what I've configured.
>>
>> 2013-09-10T12:48:50+02:00 INFO: [25403] Fetching changes for tasks using
>> MODSEQ.
>> 2013-09-10T12:48:50+02:00 INFO: [25403] Found 0 message changes in
>> @Tasks at .
>> 2013-09-10T12:48:50+02:00 INFO: [25403] Initializing state for
> collection:
>> INBOX.0-SPAM.Spamverdacht, synckey:
>> {522ef898-d424-479d-aa4b-31b1c0a80204}11
>> 2013-09-10T12:48:50+02:00 INFO: [25403] Loading state for synckey
>> {522ef898-d424-479d-aa4b-31b1c0a80204}11
>> 2013-09-10T12:48:50+02:00 INFO: [25403] Found 1 changes remaining from
>> previous SYNC.
>> 2013-09-10T12:48:50+02:00 NOTICE: [25403] Skipping 086b0452 because it is
>> not PINGable.
>> 2013-09-10T12:48:50+02:00 INFO: [25403] Initializing state for
> collection:
>> INBOX.Sent, synckey: {522ef8a6-1be8-4940-94a3-31b1c0a80204}5
>> 2013-09-10T12:48:50+02:00 INFO: [25403] Loading state for synckey
>> {522ef8a6-1be8-4940-94a3-31b1c0a80204}5
>> 2013-09-10T12:48:50+02:00 NOTICE: [25403] Skipping e7b4d8c7 because it is
>> not PINGable.
>> 2013-09-10T12:48:50+02:00 INFO: [25403] Sleeping for 10 seconds.
>>
>> A "waitinterval" of 60 would be much better. But only 10 seconds seem the
>> be accepted.. I've configured the version to 14.1 to get the "notes" sync
>> feature, too.
>
> I've tested nearly everything but cannot get this waitinterval to 60
> seconds. It remains at 10 seconds...
> Perhaps I should open a bug-ticket? I hope someone can reproduce this
> problem/behaviour.
>
> Thanks
> Sascha
> -- 
> Horde mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org


-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5849 bytes
Desc: S/MIME Signature
URL: <http://lists.horde.org/archives/horde/attachments/20130912/cd4e01e4/attachment.bin>