Editing Kieker (section)

==Monitoring cycles==

Say that you notice a slow-down when visiting a certain page on EPrints and you would like to investigate what could be the cause(s) and what could be optimised. Kieker is good at showing undesired coupling between modules and is also very good at showing "slowest paths" (when executing a web request from A to Z you can easily spot which method call(s) is/are the slowest - this could be long DB query, lots of files reads, ETC.).

The standard cycle when using Kieker is to:

* Enable Kieker on the URI you think is problematic, for your IP address only
* Restart Apache
* Go to the URI with your browser: this may be slower than usual, because Kieker is generating lots of data
* Disable Kieker
* Restart Apache
* Dequeue the Kieker monitoring data from memcached
* Use Kieker's shipped-in modules to generate releavant graphs for your analysis.

Once you start using Kieker, you will see that you can get results and graphs very, very quickly.