Am 09.02.2009 um 16:10 schrieb Tres Seaver:
> Try profiling the two requests and see what looks different.
I thought someone might say that... ;-)
As heavy upstream caching is likely to be used I hope it's not
necessary to optimise this too much. The main advantage is reducing
the number of individual requests made by the browser when it first
sees the site. But I should get more familiar with profiling.
Running locally wget gives rates of around about 50 MB/s with the view
and around 120 MB/s for a PythonScript.
> The FSFile
> object *never* stores the bits read from the filesystem, so the more
> likely case is that your view is hitting some other bottleneck.
oh, what FS things are affected by the debug-mode flag that forces
them to be reread?, ie. which objects don't reflect underlying file-
> BTW, it might be faster to compute the *filenames* in the memo, and
> return an IFilestreamIterator which chunked the response by reading
> files one at a time. Running 'cat /path/to/fsidr/*.js' in an
> os.system() call might be faster, too ;)
I quite like the iterator idea. BTW. Can I admit at this stage that I
don't really understand what the memoize method does? 8-)
Zope-CMF maillist - Zope-CMF@lists.zope.org
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests