Do those clients show the size of the documents? MarkLogic has to serialize the compressed internal structures to an XML document in order to know how big it is.
In Transmit, get rid of the "Size" column and see what happens. wunder == Walter Underwood Lead Engineer, MarkLogic Corporation [email protected] http://www.marklogic.com/ On Jun 21, 2011, at 7:24 AM, David Sewell wrote: > It does seem like the server is accessing the documents. Here is one timing > example for a directory with lots of content, accessed via WebDAV: > > Files in directory: 237 > Total XML filesize before loading: 495 MB > Total # of fragments: ca. 81000 > > Time to get directory listing: 25 sec. minimum > > Tested using both oXygen's built-in WebDAV client, and Transmit 4 from Panic, > an > efficient ftp/WebDAV client for Mac. As timings are nearly identical for > both, > the delay seems to be server-side. > > I wonder if this merits an RFE. > > David > > On Mon, 20 Jun 2011, Geert Josten wrote: > >> Hi David, >> >> Guessing a bit here, but sounds like the WEBDAV interface is accessing the >> actual documents, possibly to retrieve properties and such. It might help to >> apply fragmentation, which could help MarkLogic Server to load the data >> piece >> by piece and keep a smaller memory footprint. >> >> But perhaps someone from Mark Logic could respond with more details.. >> >> Kind regards, >> Geert >> >> -----Oorspronkelijk bericht----- >> Van: [email protected] >> [mailto:[email protected]] Namens David Sewell >> Verzonden: maandag 20 juni 2011 16:02 >> Aan: General MarkLogic Developer Discussion >> Onderwerp: Re: [MarkLogic Dev General] Viewing Documents with WebDAV >> >> On Fri, 17 Jun 2011, Danny Sokolsky wrote: >> >>> Hi Tim, >>> >>> There is nothing inherently slow about WebDAV per se, >> [...] >> >> We have consistent problems using the MarkLogic WebDAV interface with >> data directories that contain, not a large number of files, but a number >> of very large files. The directories are slow to open, whether using an >> OS client as in OS X, or oXygen's browser. The slowness seems to be >> directly related to the amount of data stored in the directory. For >> example, a directory with 136 files totalling around 250MB of XML data >> consistently takes 20 seconds or show to return a listing via WebDAV. >> >> On the database in question we have uri lexicon enabled, and my >> assumption would be that the WebDAV functionality would take advantage >> of this to compile a list of filenames in a directory quickly. I've >> never understood why the amount of data per se seems to slow down the >> WebDAV interface as much as it does. >> >> DS >> >> > > -- > David Sewell, Editorial and Technical Manager > ROTUNDA, The University of Virginia Press > PO Box 400314, Charlottesville, VA 22904-4314 USA > Email: [email protected] Tel: +1 434 924 9973 > Web: http://rotunda.upress.virginia.edu/ > _______________________________________________ > General mailing list > [email protected] > http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
