Confirm
1,199
edits
Changes
no edit summary
== Why? ==
Bugzilla's core architectural design originates in early web development times, where things were simpler. By far the largest issues which is holding back Bugzilla's responsiveness is the near complete lack of cross-request caching. Unlike most modern web applications, Bugzilla doesn't utilise a caching system such as memcached or redis to avoid regenerating the same content, and retrofitting this to Bugzilla without substantial rewriting is proving to be a difficult problem to solve.
Up until reasonably recently, Bugzilla didn't do much in terms of same-request caching: for example creating an object from its ID always required a round-trip to the database, even if the object had already been created while processing that request but in another method. Bug NNNN implemented simple object caching, with other bugs building on it make it function with more classes.
* architecture not designed to scale up to large sizes
