When trying to figure out if a plugin I had written was making the global and per job configuration page load times worse, I ended up developing this toolkit:
https://wiki.jenkins-ci.org/display/JENKINS/Tag+Profiler+Plugin It allows you to record execution times for fragments of jelly. In my case I found that I was not to blame... despite my belief that I was ;-) Others may find it a useful toolkit. Share and Enjoy -Stephen P.S. This plugin is aimed at plugin developers, I may be surprised and find everyone wants it, but my intention is that plugin developers would use it only while trying to trace performance issues in their plugins rendering. P.P.S. Due to the way hpi:run checks for modifications to jelly files *on every access* (not just per request) profiling is only really useful when running Jenkins standalone. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
