[Zope] Stability - can you give us some advice?

[tacio@psmi.com.br]

Hi,
I'm new to this list (to Zope too!)and I'm really impressed with its traffic.
This show us that this project is in active development.
In our company we are currently working to create a Web site with lots
of dynamic content, database access, webmail, etc..  so we decided to try Zope.
Although it's lack of documentation ( this would not be fair, with a search
engine we can dig out lots of useful info from the web) we experienced a
very fast development cycle. Now we're concerned about its stability. We
are almost finishing the first stage of project and some times Zope
hangs. It was  working ok, and then, all of a sudden, it just stops answers 
requests. Last time it happend we changed a DTML Method to a DTML Document
and it worked again (if you like i'll try to tell you exactly what was happenning). 
So, I'd like some advice to make it more stable. ( or tell me what i might
be doing wrong)

Our environment:

   OS: Debian GNU/Linux 2.2 (Potato) - Kernel 2.2.16
   Plataform: Dual PentiumIII - ASUS motherboard - scsi Adaptec AIC-7892)
   Python: got from Debian -  python-base_1.5.2-10_i386.deb
   Zope: got from Debian -  zope_2.1.6-5_i386.deb
   DB: Postgresql V7.0.2 - compiled and installed by hand -> tools from Debian, (make,gcc,..)
   DB-DA:  zope-pygresqld 0.3rjr2-1
   Front-End: Apache 1.3.12 + mod_ssl + mod_proxy + mod_rewrite
              (with mm-1.1.3 Shared Memory Library ) 
              Install type : DSO - Dynamic shared Object
              (compiled and installed by hand -> tools from Debian, (make,gcc,..)

Some questions: (with stability in mind..)

  1) Should we try Zope 2.2.0b3 instead of 2.1.6 ?
  2) Should we avoid using packaged versions of Zope?
  3) Should we try ZPoPyDA as a DA to Postgresql?
  4) Could you give us some advices on good DTML coding: what should
     we avoid doing, what is a must, for example, whether or not (or when)
     to generate urls for objects (http://www.zope.org/Members/jim/ObjectURLs)

Thanks a lot for your attention,

Tacio AGSantos
tacio@psmi.com.br