Per Jessen wrote: > I have yet to study the performance-impact in thawing a Conf object, but > given that I really need the correct per-user behaviour, it's not overly > important.
Just a quick follow-up - instead of freeze/thaw I tried using store retrieve, which cuts down on the memory footprint. The file is written once and then read many times by a number of children, and I can just let the file-system cache it as it sees fit. Alternatively, I tried writing the file to /dev/shm/, but I haven't seen any major differences when compared to writing to disk. /Per Jessen, Zurich
