[horde] Max memory message for ActiveSync

Michael J Rubinsky mrubinsk at horde.org
Wed Oct 16 13:19:51 UTC 2013


Quoting simon at simonandkate.net:

>> On 16 Oct 2013, at 8:56 pm, lst_hoe02 at kwsoft.de wrote:
>>
>>
>> Zitat von Simon Wilson <simon at simonandkate.net>:
>>
>>> ----- Message from Michael J Rubinsky <mrubinsk at horde.org> ---------
>>>    Date: Tue, 15 Oct 2013 10:36:46 -0400
>>>    From: Michael J Rubinsky <mrubinsk at horde.org>
>>> Reply-To: mrubinsk at horde.org
>>> Subject: Re: [horde] Max memory message for ActiveSync
>>>      To: horde at lists.horde.org
>>>
>>>
>>>> Quoting Simon Wilson <simon at simonandkate.net>:
>>>>
>>>>> Michael R, what does this mean in the logs:
>>>>>
>>>>> 2013-10-15T11:07:59+00:00 DEBUG: Maximum memory usage for
>>>>> ActiveSync request: 24297544
>>>>>
>>>>> 2013-10-15T21:11:23+10:00 DEBUG: Maximum memory usage for
>>>>> ActiveSync request: 45539816
>>>>>
>>>>> Seeing a few of them, wondering if it is a significant notification.
>>>>
>>>> It's a dubug message, indicating the maximum amount of memory used
>>>> during the processing of the activesync request. I added it to aid
>>>> in some refactoring I was doing to improve memory usage and
>>>> performance.
>>>>
>>>> --
>>>> mike
>>>>
>>>> The Horde Project (www.horde.org)
>>>
>>>
>>> Mike - one other thing from the device logs. Up to about 15 times in
>>> a minute or so for each of my devices, then with pauses of up to 10
>>> / 15 minutes, I see a lot of lines that start like this:
>>>
>>> 2013-10-16T20:38:44+10:00 INFO: [12961] Replacing SYNC_CACHE entry
>>> for user simon and device SEC10D1C297BE813:
>>> a:11:{s:18:"confirmed_synckeys";a:0:{}s:17:"lasthbsyncstarted";i:1381919893;s:17:"lastsy
>>>
>>> I haven't done the whole line, because the single line contains
>>> nearly 90KB of text. As a result the device logs grow very rapidly -
>>> I have seen daily device logs at over 250MB. I'm assuming it is not
>>> all transmitted to/from the device as I would have blown my data
>>> allowance if it was.
>>>
>>> Is this normal to be repeating this so often with such large  
>>> amounts of data?

That represents the sync cache, and it is necessary to update it any  
time one of the values change. So, yes, it is not uncommon to see that  
fairly often.


>>> E.g. from one log, grepped for the SYNC_CACHE string:
>>>
>>> 2013-10-16T10:38:08+00:00 INFO: [12957] Replacing SYNC_CACHE entry...
>>> 2013-10-16T10:38:08+00:00 INFO: [13225] Replacing SYNC_CACHE entry...
>>> 2013-10-16T20:38:08+10:00 INFO: [12957] Replacing SYNC_CACHE entry...
>>> 2013-10-16T10:38:09+00:00 INFO: [13225] Replacing SYNC_CACHE entry...
>>> 2013-10-16T10:38:09+00:00 INFO: [17557] Replacing SYNC_CACHE entry...

There are 3 different threads represented just in those 5 lines.  
Sounds like some process is either stuck, or perhaps you caught the  
log while there were a number of updates being sent/received.

-- 
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/20131016/a448b85a/attachment.bin>


More information about the horde mailing list