File IO question.
oo1z at yahoo.com
Thu Jul 15 19:12:42 CEST 2004
I'm hoping that someone might have some pointers or
examples on how to proceed with a solution to the
A test application, which produces a trace file, is
being run for very long periods of time. Say 72 hours
The application is often running on older PCs that
have relatively small hard drives in comparison to
to how big the trace file can become.
The trace files tend to accumulate as they're not
always deleted once archived to a network database,
and often times a machine will crash in the middle of
very long test due to the hard drive filling up.
There are dozens of PCs being used for the tests so
buying bigger hard drives isn't really feasible. And
I'm guessing the hard drives would fill up eventually
anyway regardless of the size of the hard drive, the
crashes just wouldn't occur quite as often.
The nice thing is that the trace files compress quite
I messed around with the mmap and file object stuff
as well as the win32 extensions thinking that I could
extract and compress the data that was being written
the trace file, by the application, in chuncks.
Although I was able to get it to work on a contrived
setup, it didn't work when used with the real
Any hints on how to get something similar to the above
to work or recommendations on alternate solutions
be *greatly* appreciated.
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
More information about the Python-list