On Monday 23 December 2002 12:22 pm, borge@tsar.no wrote:
We now do wonder if zope's "undo" possibility is an explanation to this large increase in data.fs; this since zope holds the states inbetween the transactions (four transactions for each question).
(3k per question)/(4 transactions per question) = 800 bytes per transaction. This is normal if each transaction modifies your emloyee object, and each employee is roughly 800 bytes in size. You could use sessions to combine this into one transaction - storing intermediate changes in a volatile session object. This would give you a factor of 4 space saving.
If it is this undo possibility that causes the large increase in data.fs
Thats just the way FileStorage works. Yes, it is used to implement undo.
we would like to know if it is possible to get around this "undo" tracking af zope.
There are some storages that dont support undo, but nothing that is production-ready :-( Your best option is to pack regularly using cron. -- Toby Dickenson http://www.geminidataloggers.com/people/tdickenson