Tools, Tips, and Techniques for Approaching Scalability
am I in the right room?
inability to grow with traditional caching solutions,
icky system performance, crashitis, log-o-phobia,
hardware anemia, mashup mayhem, diminishing
conﬁdence in your abilities as plone integrator or
administrator, where do I start migraines, all the rest of the
talks look boring, this room has better internet connectivity, I
have no clue what I’m doing here
A responsive, scalable Plone setup has little to do with
The browser is the cheapest, easiest caching tool
at your disposal, Daniel-son. It’s time to show the
world you are the developer I know you can be...
Oh, CacheFu you have been a great
leader and I wish I would have taken the
time to ﬁgure out how caching really
works. I’m afraid I will fail you, never fully
understanding the 304. Shame!
Serve STATIC content from a STATIC web server
to unload plone, provide faster
response time to initial requests, 5200
and enable simpler caching
user.gif link_icon.gif poo.gif
HTTPD RewriteRule ^/(.*)portal_skins/mysite_images/(.*) /mysite_images/$2 [L]
ZEO is perfect for object
oriented access, but it needs
a little help with other data
ZEO & CO.
RESTARTing zope is NOT a SIN
sometimes its just easier...
a PACKED zodb is a HAPPY zodb
beware of backup side effects
deploy with 1-step
fabrics’ rolling blackouts
ZEO & CO.
watch the disk
ZEO & CO.
Living in the Cloud
I will automate a modular
installation of everything
I will not do anything manually
that could be done
automatically, which is everything
I can trigger unscheduled
processes anytime, from
I appreciate that scaling is hard:
the cloud offers options, not
‣ Always setup system and error monitoring ﬁrst
‣ Choose the right software for YOUR hardware
‣ Use as many zopes as possible but no more
‣ Do it like a ﬂickr engineer
‣ Don’t make zope handle unnecessary requests
‣ Never underestimate the importance of a
proper disk-RAM partnership
‣ Design processes to be able to run from
anywhere, at anytime, on any machine
All this and more at