------_extPart_001_01C88929.BEA2C37A
Content-Type: text/plain;
	charsets-ascii"
Content-Transfer-Encoding: quoted-printable

Last week I posted a question about incorrect file sizes coming back
incorrectly from File.size? for really large files.  I changed my script
to use the win32 version, which returns the correct sizes, and now the
script is unacceptably slow. The bottleneck is the File.size call. My
scripts startup went from about a minute to, well I don't know because
it's never finished.  I'm walking a file path that is somewhat indirect,
but the other file operations perform well.  I'm reading files, using
UNC paths, through samba on linux boxes that mount a giant file system
through fiber.

 

So anyway, does anyone have any alternatives?

 

________________________________

Carey Nation <mailto:carey.nation / cnn.com>  

Lead Software Engineer

CNN BEST

Broadcast Production Systems

Video Solutions Group

(404)827-2935 (wk)

(404)824-0033 (cell)

________________________________

 


------_extPart_001_01C88929.BEA2C37A--