On 18/09/15 07:54, Thorsten Möllers wrote:
I don't think this is an option. We have a huge set of running jobs, a
lot of them short lived, so I try to keep the cost for a single job
exiting minimal. As I see it, currently the memory allocated in my
plugin for a single build is O(1), since the hierarchy structure is
more or less static. The execution time to handle a single
notification is also O(1), for the same reason. Going through all
builds would add an operation O(n), n being the number of currently
running builds, which is quite huge in our system. Since a lot of our
builds are short-lived, this task would be executed quite frequently.
Now here I might have to correct myself. The additional memory
allocation could easily add more complexity than running through the
list of all running jobs. Probably I should run some performance tests
for both approaches in a staging environment.
Br,
Thorsten
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/55FBB79A.80003%40thorzten.de.
For more options, visit https://groups.google.com/d/optout.
