Replying to Ard here, as I think he may have been referring to this thread
;-)

On 12/17/07, Ard Schrijvers <[EMAIL PROTECTED]> wrote:
> > > 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.
> >
> > It does not provide information about what the query was, but
> > the request log of the repository does tell you how long it
> > took to execute a SEARCH method.
>
> No, the SEARCH method won't be slow (unless you have strange queries and
> the number of documents exceed 1 million), but I don't think you have
> that yet. I am quite sure it can be found in the number of round-trips
> to and from the repository for opening some perspective.
>
> I does however differ a lot if for example workflow is already set on
> the documents you are browsing: if not (for example, you had a content
> migration, but not workflow), then on each first time click on a doc, a
> new workflow must be created, and many round trips instantiated. After
> this, there should be seen caching, because this is added a few versions
> ago.
>
> Also wondering, what is the setup you are experiencing this: is it your
> local laptop, or something else?
>

Yes, I've seen some speed-up with documents where workflow already exists
(missing workflow is a performance hit especially with large collections as
the cms iterates over every doc looking for the next free id, which suggests
best practice after an import is to run a tool over the repo to force
creation of id).

The setup where I'm seeing slowdowns is on a fairly beefy solaris box which
I'd normally expect to perform much better. Ironically, on my local laptop
the CMS is blisteringly fast.


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

Reply via email to