|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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.
Well, it's less than a second we will gain but it is quite easy to change that the messages will be read on demand (but it has the drawback of a synchronized piece of code during Jenkins runtime, this is not needed currently). I think over the Christmas vacation I'll have some spare time...
Would it help if we make some performance tests with Jenkins? I'm planning a lecture/project about "testing enterprise applications" in the summer term in our department: maybe my master students can set up a performance test suite to detect existing bottle necks. These tests could also run in CI to prevent that the performance degenerates if a new feature is added...