24 Mar 2001 13:14:45 - INFO - PUT (time: 94874 ms) URI = /files/archives/2712.JPG
24 Mar 2001 13:14:49 - INFO - OPTIONS (time: 57 ms) URI = /
24 Mar 2001 13:14:49 - INFO - PROPFIND (time: 463 ms) URI = /
24 Mar 2001 13:15:13 - INFO - PROPFIND (time: 21509 ms) URI = /files
24 Mar 2001 13:18:02 - INFO - PROPFIND (time: 163203 ms) URI = /files/archives
This is what happens when 1000 files are in a folder in IE :)
Dan Diephouse
Remy Maucherat wrote:
> Quoting "Kurapati, Rama" <[EMAIL PROTECTED]>:
>
> > Hi:
> >
> > I have a Folder TEST with 500 sub folders, each containing 100 files,
> > all
> > of same size 400 bytes. It is strange that it takes only 40-90 ms for
> > the
> > first 2 thousand files and afterthat the time is gradually increasing.
> > After
> > reaching 5000 files - 900 ms , 10000 files it is taking 4000-7000 ms
> > and it
> > continuous to grow.
>
> I suppose you're taking about the time needed to do a PROPFIND enumerating all
> those resources.
> Could you give more details about the request being made ?
>
> As you know, the response to that request is XML, and is quite verbose
> (especially a request for all properties). Therefore, it takes a long time to
> generate, and then a long time to parse at the other end, since it's rather
> likely that the client will use DOM to parse.
> For one resource, the size of the XML generated for a PROPFIND with allprop is
> about 3.2 K. So for 10 000 resources, that's 32 M ... Also, that figure is
> bound to grow a bit when Delta V is added.
>
> One thing which can be done to improve performance with large amount of
> resources is add more memory and raise the cache limits (this is configurable
> right now, but it could be a factor).
>
> The solutions to this can only come from reducing the amount of XML generated.
> You can :
> - splitting resources across multiple collections
> - avoid doing PROPFIND infinity requests (which is Slide are converted to Depth
> 3 - but apparently this is still too much, and this has to be made configurable)
> - only do PROPFIND requests asking for specific properties (IE does this, and
> this cuts th response size by 3-5)
>
> > I have been trying to a find fix, but i couldn't get any clue.
>
> Remy
