[kronolith] new event gui need two seconds to "load"

[Samuel Wolf]

Zitat von Simon B <simon.buongiorno at gmail.com>:

> On 2 Jun 2014 11:23, "Samuel Wolf" <samuel at sheepflock.de> 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


-------------- next part --------------
==> click on new event

21:45:14.172 DOM-Neuberechnung: 0.51ms Funktion KronolithCore.openTab, kronolith.js Zeile 1290
21:45:14.173 DOM-Neuberechnung: 0.23ms Funktion RedBox.setOverlaySize, redbox.js Zeile 109
21:45:14.174 DOM-Neuberechnung: 0.48ms Funktion RedBox.setOverlaySize, redbox.js Zeile 109
21:45:14.174 DOM-Neuberechnung: 0.34ms Funktion getDimensions, prototype.js Zeile 4038
21:45:14.174 DOM-Neuberechnung: 0.66ms Funktion getDimensions, prototype.js Zeile 4038
21:45:14.175 DOM-Neuberechnung: 0.3ms
21:45:14.175 POST https://example.com/horde/services/ajax.php/kronolith/listTopTags [HTTP/1.1 200 OK 205ms]
21:45:14.176 GET https://example.com/horde/themes/default/sounds/doorbell.wav [HTTP/1.1 200 OK 1ms]
21:45:14.176 GET https://example.com/horde/themes/default/sounds/gnid3.wav [HTTP/1.1 200 OK 2ms]
21:45:14.177 GET https://example.com/horde/themes/default/sounds/jetsndb.wav [HTTP/1.1 200 OK 36ms]
21:45:14.178 GET https://example.com/horde/themes/default/sounds/reminder.wav [HTTP/1.1 200 OK 36ms]
21:45:14.178 GET https://example.com/horde/themes/default/sounds/theetone.wav [HTTP/1.1 200 OK 34ms]
21:45:15.733 DOM-Neuberechnung: 0.24ms
21:45:15.733 DOM-Neuberechnung: 0.48ms

==> new event gui

~ 1600ms
-------------- next part --------------
==> click on new event

21:44:47.526 DOM-Neuberechnung: 0.62ms Funktion KronolithCore.openTab, kronolith.js Zeile 1290
21:44:47.527 DOM-Neuberechnung: 0.38ms Funktion RedBox.setOverlaySize, redbox.js Zeile 109
21:44:47.528 DOM-Neuberechnung: 0.69ms Funktion RedBox.setOverlaySize, redbox.js Zeile 109
21:44:47.529 DOM-Neuberechnung: 0.35ms Funktion getDimensions, prototype.js Zeile 4038
21:44:47.529 DOM-Neuberechnung: 0.7ms Funktion getDimensions, prototype.js Zeile 4038
21:44:47.530 DOM-Neuberechnung: 0.26ms
21:44:47.530 POST https://example.com/horde/services/ajax.php/kronolith/listTopTags [HTTP/1.1 200 OK 318ms]
21:44:47.203 getAttributeNode() sollte nicht mehr verwendet werden. Verwenden Sie stattdessen getAttribute(). prototype.js:2827
21:44:47.203 Das specified-Attribut von Attributen sollte nicht mehr verwendet werden. Es liefert immer true. prototype.js:2828
21:44:47.533 GET https://example.com/horde/themes/default/graphics/tab.png [HTTP/1.1 200 OK 282ms]
21:44:47.534 GET https://example.com/horde/themes/default/graphics/button-default.png [HTTP/1.1 200 OK 281ms]
21:44:47.769 DOM-Neuberechnung: 0.34ms
21:44:47.770 DOM-Neuberechnung: 0.6ms
21:44:47.770 GET https://example.com/horde/themes/default/sounds/doorbell.wav [HTTP/1.1 200 OK 2ms]
21:44:47.771 GET https://example.com/horde/themes/default/sounds/gnid3.wav [HTTP/1.1 200 OK 4ms]
21:44:47.772 GET https://example.com/horde/themes/default/sounds/jetsndb.wav [HTTP/1.1 200 OK 5ms]
21:44:47.773 GET https://example.com/horde/themes/default/sounds/reminder.wav [HTTP/1.1 200 OK 549ms]
21:44:47.774 GET https://example.com/horde/themes/default/sounds/theetone.wav [HTTP/1.1 200 OK 282ms]
21:44:48.064 DOM-Neuberechnung: 0.06ms Funktion Form.Element.Methods.activate, prototype.js Zeile 6031

==> new event gui

~ 500ms