File: README.performance

package info (click to toggle)
zope-speedpack 0.3-2
  • links: PTS
  • area: main
  • in suites: sarge
  • size: 156 kB
  • ctags: 66
  • sloc: python: 421; sh: 60; makefile: 38
file content (38 lines) | stat: -rw-r--r-- 1,146 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
Some performance tipps for productive servers

DON'Ts:

 * Don't run zope in debug mode if you don't want to develop products or debug
   problems. In Zope 2.7 it's enabled per default. Disable the debug mode in
   $INSTANCE_HOME/etc/zope.conf

 * Don't use VerboseSecurity unless you need to debug security issues.

 * Don't use/enable a profiler like ZopeProfiler.

 * Don't add too many pathes to a skin.

DOs:

 * Use this SpeedPack product.

 * Use Python 2.3.3+ (it's 10-30% faster compared to Python 2.1)

 * Increase the ZODB cache size but don't make it too large! If your machine
   is out of physical ram zope is running terrible slow. About 2k to 10k are
   good.

 * Use the C implementation of the security machine.
 
 * Cache your site
 
 * Use the PlacelessTranslationService. Localizer + TranslationService are
   slower due the zope traversals and PTS includes my unicode aware speed up
   patch for TALInterpretor.StringIO.

 * Use Caching, read http://www.clearwind.ca/talks/profiling_and_caching.pdf

 * Use a ZEO Cluster with a SQUID proxy as load balancer.

 * Did I mention caching?