The more important consideration by far is to avoid triggering loading of build records. Since Jenkins does not use a database, test results for a given build can only be obtained when the whole build (`Run`) is in memory. This is a large object, and to load it requires reading and parsing a `build.xml` file, which is relatively expensive. By default a `SoftReference` is used to hold a (completed) build record, so that when heap is running short some will be evicted. Thus any frequently-accessed GUI page which attempts to reference historical builds, if not written carefully, could wind up repeatedly forcing build reloading on a loaded server.
-- 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/CANfRfr0GUXPA_C8CZZd6e%3DX0Nhbe9GXqJ_MfMPtyGiWgOMO9bQ%40mail.gmail.com.
