Confirmed users
1,198
edits
BMO/performance: Difference between revisions
→What will we be doing?
| Line 39: | Line 39: | ||
While the BzAPI proxy consumers themselves should consider the impact these calls have on BMO and implement caching mechanisms, it's understandable why this doesn't always happen (I've seen many a quick-and-dirty solution quickly turn into production-level usage without refactoring to lessen its impact). Once the REST services are integrated with Bugzilla, we plan on caching identical requests within a set time frame to guard against accidental BzAPI-driven DDOSing of BMO. | While the BzAPI proxy consumers themselves should consider the impact these calls have on BMO and implement caching mechanisms, it's understandable why this doesn't always happen (I've seen many a quick-and-dirty solution quickly turn into production-level usage without refactoring to lessen its impact). Once the REST services are integrated with Bugzilla, we plan on caching identical requests within a set time frame to guard against accidental BzAPI-driven DDOSing of BMO. | ||
One change in the pipeline which should net client-side benefits is the upgrade of our core javascript library, YUI, from version 2 to version 3. YUI3 footprint on the browser is significantly less when compared with YUI2, with a strong focus on lazy-loading of libraries. Yahoo are performing the work for us here, in {{bug|453268}}. | One change in the pipeline which should net client-side benefits is the upgrade of our core javascript library, YUI, from version 2 to version 3. YUI3's footprint on the browser is significantly less when compared with YUI2, with a strong focus on lazy-loading of libraries. Yahoo are performing the work for us here, in {{bug|453268}}. | ||
== What isn't the problem? == | == What isn't the problem? == | ||