I always use Charles (not free) [1].For repository traffic and traffic between browser you can also use it. You'll see very easy which calls are slow, or which calls are done over and over (while they might be cached. I for example found with this tool for a certain customer ones that for every call, they fetched a gigantic users.xml file from the repository over and over)
Also incorrect headers for images and css are easily spotted, resulting in less snappiness for your pages. Furthermore, for your browser traffic only, you might want to take a look at YSlow (add-on) [1] http://www.xk72.com/charles/ Regards Ard > > Hi, > > Aside from using jmeter [1] and tcpmon to test and diagnose > HippoCMS, are there any other tools/utilities/methodologies > the Hippos use? > > In particular I'd love to know of a straightforward way to > see if DASL queries on the repo are performing. Unfortunately > most tools are limited to HTTP HEAD/GET/POST, so the > webdav-specific stuff is difficult to test. > > [1] > http://lists.hippo.nl/pipermail/hippocms-dev/2007-October/003771.html > [2] > http://lists.hippo.nl/pipermail/hippocms-dev/2007-December/004022.html > > > Andrew. > -- > Sourcesense: Making sense of Open Source > Tel: +44 (0)870 741 6658 Fax: +44 (0)700 598 1135 > Web: http://www.sourcesense.com/ > ******************************************** > Hippocms-dev: Hippo CMS development public mailinglist > ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
