{"id":55,"date":"2009-08-14T07:42:31","date_gmt":"2009-08-14T11:42:31","guid":{"rendered":"http:\/\/screwedbydesign.com\/blog\/?p=55"},"modified":"2009-08-14T07:42:31","modified_gmt":"2009-08-14T11:42:31","slug":"this-week-in-perf-aug14","status":"publish","type":"post","link":"http:\/\/screwedbydesign.com\/blog\/2009\/08\/this-week-in-perf-aug14.php","title":{"rendered":"This Week in Perf – Aug. 14th Edition"},"content":{"rendered":"

The Firefox team has recently started using small, well-scoped projects<\/a> as a way to speed development and to better split up and coordinate tasks among many developers.\u00a0 Since these projects are typically small and have well defined goals, we’re also using them train ourselves to communicate more effectively<\/a> and more often (has it really been three years since I last blogged\u203d<\/span>) about what our team is up to.<\/p>\n

My project for the last couple weeks has been startup performance<\/a> – mainly focusing on identifying and fixing areas where file IO is causing us pain.\u00a0 Working with David<\/a>, Dietrich<\/a>, Drew<\/a>, Vlad<\/a> and Taras<\/a>, we’ve found<\/a> and have started working on some potential wins.<\/p>\n

I didn’t have much time this week due to a cold and dealings with lawyers, but I started wrapping my head around the component loader in order to try having components packaged as a single JAR so that we can cut down on individual file reads during cold, non-fastload backed startups and stat<\/code>s in the warm case.<\/p>\n

As far as what’s on tap for the next week I need to:<\/p>\n