- Profiling Plone
- Optimizing ZEO and threads
- Debugging slow threads in production
- Memcached as session storage
- Input/output performance of the server
- Tuning complex configurations
- Reducing memory usage
- Large files
- LinguaPlone and multi-lingual sites
- Sessions and performance
- ZServer thread count
Tips for Plone performance tuning and making your add-on product and customizations faster.
For multicore systems, which basically all production systems nowadays are, you might want to optimize Python threading vs. processes. You may also tune how many Python interpreter instructions are run before doing green thread switches in the interpreter.
Storing sessions in ZEO/ZODB does not scale well, since they are very prone
ConflictErrors if there is considerable load on the system.
Memcached provides a more scalable session backend.
For more information, see lovely.session add-on product.
<mcdonc> well, the example has await at about 40X svctime.. that's pretty shitty <mcdonc> i mean that box was useless
These tips are especially critical when running Plone on low-memory virtual private server (VPS). But using the memory tips below, and some filesystem and operating system tweaks, it is also perfectly possible to run Plone on an ARM-based Android stick, or a Raspberry Pi. See http://polyester.github.io/
buildout.cfg to declare which .po files are loaded on the start-up:
[instance] ... environment-vars = PTS_LANGUAGES=en fi
How to offload blob processing from Zope:
Do not use
LanguageIndex, and update your
LinguaPlone to version
Write transactions much worse performance-wise than read transactions.
By default, every login is a write transaction. Also, Plone needs to update the logged-in user's session timestamp once in a while to keep the session active.
With a high amount of users, you may start seeing many
(read conflicts) with ZODB.
There are some tricks you can use here:
This specifies how many requests one ZEO front-end client (ZServer) can handle.
The default set by buildout default is 2.
[client1] recipe = plone.recipe.zope2instance .... zserver-threads = 5
Find good value by doing performance testing for your site.
Increasing thread count is useful if your Plone site does server-to-server traffic and your Plone site needs to wait for the other end, thus blocking Zope threads.
XSendFile is an enhancement over HTTP front end proxy protocol which allows offloading of file uploads and downloads to the front end web server.
More info for Plone support: