The Performance Team is interested in high-performance and high availability of Tiki. Tiki should not cause performance bottlenecks on shared hosting, should have options to allow it to be used in highly scalable clustered environments, and high-availability configurations.

Release responsibilities

• Monitor performance for each release before .0 is released
  • Google PageSpeed
  • Yahoo! YSlow
  • etc.

Ongoing

• Monitor *.tiki.org sites
  • http://www.webpagetest.org/
  • http://www.showslow.com/
• Performance challenge

Wishes

• Calendar performance
• PluginConvene seems to be slow
  • http://dev.tiki.org/Next+Release -> Execution time: 9.78 secs - Memory usage: 52.71MB - 1177 database queries used in 0.3 secs
  • http://dev.tiki.org/Where+to+commit -> Execution time: 1.07 secs Memory usage: 54.92MB 1237 database queries used in 0.2 secs

Projects

• Review *.tiki.org Analytics Team (Google Analytics and Piwik tracking, server logs, etc.) and discover if/what are the performance issues. Especially broken links, and lacking robots.txt, Canonical, etc.
  • http://piwik.org/docs/page-speed/ -> Page speed reports could be embedded in wiki pages
• Ask for performance feedback from the people Testing Tiki installations on major Shared Hosting companies

Related pages

• dev:Performance
• doc:Performance
• http://lognormal.github.com/boomerang/doc/use-cases.html

Page Aliases

Performance