2015-09-27 9:00 GMT-07:00 Jesse Glick <jgl...@cloudbees.com>: > On Sun, Sep 27, 2015 at 12:18 AM, martinda <martin.danjo...@gmail.com> > wrote: > > I have 141 projects, > > 30,373 builds, and 1,073,591 junit XML test results. It took me over 20 > > minutes of CPU time to get these values by querying the file system. > > Yes, build storage is a well-known architectural problem. PR 1641 will > not help you here. > > > Will Jenkins 2.0 have database backend? > > No, the changes required are too big. There is no way to do it that > quickly. I think we *should* do these changes sooner or later. For me > this seems both more important and more disruptive than the code > changes currently being discussed for 2.0. >
Yeah, I tend to agree. It is an important issue, but as Jesse says, I'm afraid it's too disruptive than all the boundaries that we operate in. We should still take it on, but it shouldn't be tied to Jenkins 2.0. -- Kohsuke Kawaguchi -- 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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAN4CQ4yTKFtpx5FCkqszYdd94fzu8FSjC%3DiT4cR7beSWzkAG_Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
