Re: new event gui need two seconds to "load"

Quoting Samuel Wolf <[email protected]>:

> Zitat von Jan Schneider <[email protected]>:
>
>> Zitat von Samuel Wolf <[email protected]>:
>>
>>> Zitat von Simon B <[email protected]>:
>>>
>>>> On 2 Jun 2014 11:23, "Samuel Wolf" <[email protected]> wrote:
>>>>>
>>>>> Hello,
>>>>>
>>>>> first time I edit or create a new event the gui shown up immediately.
>>>>> But then, for the next event the window need two seconds to load
>>>>> (nothing happens) after the click to "New Event".
>>>>> It is absolutly reproducible.
>>>>>
>>>>> After logout and login, the first time create a new event is quick and
>>>>> all other need the two seconds again.
>>>>>
>>>>> Any idea?
>>>>
>>>> Sounds like an apache or php memory issue.  What does your log say?
>>>
>>> Nothing, no errors in horde or apache log.
>>> php.ini -> memory_limit = 512M
>>>
>>> Found out change to IMP/Nag/... and go back to kronolith help as  
>>> well, but only for the first "new event".
>>> Attached some browser debug benchmarks, I see this on 4 different  
>>> horde installations.
>>>
>>>>
>>>> Simon
>>
>> Those stats don't help at all, because they don't explain why the  
>> rendering takes 1600ms. Reading the logs, the second rendering  
>> should even be faster, because two icons are not loaded which  
>> already made up >500ms in the first request.
>
> Apache log:
> ==> click on new event
> 10.23.1.88 - - [03/Jun/2014:10:09:43 +0200] "POST  
> /horde/services/ajax.php/kronolith/listTopTags HTTP/1.1" 200 731  
> "https://example.com/horde/kronolith/" "Mozilla/5.0 (X11; Linux  
> x86_64; rv:29.0) Gecko/20100101 Firefox/29.0"
> ... 2 seconds ...
> ==> GUI visible
>
> Horde Debug log:
> ==> click on new event
> 2014-06-03T10:11:40+02:00 DEBUG: HORDE [kronolith] SQL  (0,0005s)
>         SELECT alarm_id, alarm_uid, alarm_start, alarm_end, alarm_methods,
>           alarm_params, alarm_title, alarm_text, alarm_snooze, alarm_internal
>           FROM horde_alarms WHERE alarm_dismissed = 0 AND  
> ((alarm_snooze IS NULL
>           AND alarm_start <= '2014-06-03 08:11:40') OR alarm_snooze <=
>           '2014-06-03 08:11:40') AND (alarm_end IS NULL OR alarm_end >=
>           '2014-06-03 08:11:40') AND (alarm_uid IS NULL OR alarm_uid = '' OR
>           alarm_uid = 'horde-admin') ORDER BY alarm_start, alarm_end  
> [pid 4199 on line 320 of "/usr/share/php/Horde/Db/Adapter/Mysqli.php"]
> 2014-06-03T10:11:40+02:00 DEBUG: HORDE [kronolith] Max memory usage:  
> 3670016 bytes [pid 4199 on line 618 of  
> "/usr/share/php/Horde/Registry.php"]
> ... 2 seconds ...
> ==> GUI visible
>
> Jan, you don't see this?
> All my installations has shared system calenders, could that be the  
> problem (don't make really sense)?
> All users affected, tested with several browser and os.


For what it's worth, I've seen this for a while, but have absolutely  
no idea what the cause is.

-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject

-- 
kronolith mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]