The plone.org and plone.net websites are the first confrontation with Plone for most users. It is important that they perform well and are stable. With almost 4 million page views per day and thousands of LDAP users plone.org and plone.net are examples of a complex deployment setup requiring LDAP, caching and load balancing - all on a single machine. I will describe how the Plone websites are build and how those practices can be applied to other sites, making it possible to scale upwards to bigger sites or make smaller sites more efficient.
14. Bluffing
• ~ 150k page views per day
• Plone is not nearly fast enough
• Fake it!
15. Varnish vs Squid
• Squid help enormously
• Varnish helped even more
• ~80% cache hit rate
• CacheSetup makes it possible
16. Source Control
• Subversion
• Synchronised to svn-mirror.plone.org
• Access control via LDAP
• Reporting to CIA and mailing lists
17. Who are you ?
• Authentication required for services
• Duplication is evil
• Single account database
18. LDAP everywhere
plone.org dev.plone.org
LDAP svn commit
LDAP LDAP
repllication mails
server server
plone.net svn.plone.org
19. •
•
per month
28971 accounts
~ 1000 new accounts
0
7,500
15,000
22,500
30,000
December 2005
February 2006
April 2006
June 2006
August 2006
LDAP Statistics
October 2006
December 2006
LDAP accounts
February 2007
April 2007
June 2007
August 2007
21. No Worries Mate
• Spam on dev.plone.org
• Spam on lists.plone.org
• Spam on paste.plone.org
• Postgres and Varnish stability
• Robots are coming to get us