On Tue, Mar 25, 2014 at 8:23 AM, Artur Szostak <[email protected]> wrote: > So much for lazy loading then.
The stack trace you quoted did not involve loading build records, so that has nothing to do with lazy loading. You may indeed have some problem with Jenkins loading (far) too many build records, but your single stack trace did not indicate that. You would need to review many stack traces taken at intervals, or even run a Java profiling tool, to see what is being loaded by whom and therefore what code is to blame—perhaps some defective plugin, or some rarely used core feature which was never optimized. (For I/O problems, strace and similar tools can be invaluable.) Certainly a two-hour startup is pathological, and <1000 jobs is quite routine. Please remember that you are posting to the dev list. If you have done a full investigation on your installation’s startup behavior and pinpointed something Jenkins is doing which is especially slow and which it need not do, then that is interesting—something deserving a report in JIRA (if reproducible against Jenkins trunk builds) and perhaps a pull request. -- 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/d/optout.
