Re: firedocs 1.3.7 with lenya 2.1.x

Hi Andreas,

Andreas Hartmann <[email protected]> schrieb am 18.11.2010 13:52:11:

> Von: Andreas Hartmann <[email protected]>
> An: [email protected]
> Datum: 18.11.2010 13:53
> Betreff: Re: firedocs 1.3.7  with lenya 2.1.x
>
> Hi Martin,
>
> Am 18.11.10 08:01, schrieb [email protected]:
> > Andreas Hartmann<[email protected]>  schrieb am 17.11.2010 13:24:20:
> >
> >> Von: Andreas Hartmann<[email protected]>
> >> An: [email protected]
> >> Datum: 17.11.2010 13:25
> >> Betreff: Re: firedocs 1.3.7  with lenya 2.1.x
> >> Am 16.11.10 15:04, schrieb [email protected]:
> >>> I try to run firedocs 1.3.7 with lenya 2.1.X  and the
> >>> defautlfiredocs-publication on base of the description in the lenya
> > wiki.
> >>>
> >>> If the pub contains only a few documents it works fine…with many
> > documents
> >>> it requires  very much time (near one minute on my system) till
> > firedocs is
> >>> ready to edit.
> >>>
> >>> Ist this behavior standard.?  Any  experience?
> >>
> >> I suspect that this is related to the assets/children list generation,
> >> which is probably slower for large site trees.
> >>
> >> Can you check which requests take particularly long, e.g. using
Firebug?
> >
> >
> >   I can confirm your suspect. By disable the children-collection
generation
> >   in the module-file atom/jx/children.jx
> >   firedocs load very fast. My test-pub has many chidren but no assests.
> >   Maybe the same behavoir with assets. But no test yet.
>
> at first glance I don't see anything suspicious in the code. It might be
> that the meta data cache is too small for the amount of documents, maybe
> you can try to increase it.

  I increased the meta data cache unfortunately  without any effect.

> Would it be possible for you to send me a ZIP of your pub incl. content
> so that I can run some tests? TIA!

 (See attached file: content.zip)

Thanks for testing!

Regards
Martin

>
> -- Andreas
>
>
> --
> Andreas Hartmann, CTO
> BeCompany GmbH
> http://www.becompany.ch
> Tel.: +41 (0) 43 818 57 01
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>