On Wednesday 06 February 2008, Matthew Dillon wrote:
[...]
quoted text
>     * I can't fix the write performance issue due to the way the cluster
>       localization and spike code works.

Just curious: what was the write performance issue? I mean, what was the use 
case and how bad was the performance? I don't think it was described in any 
detail in your past HAMMER update mails, but please point me to the mail if 
it was.

quoted text
>     Everything else now works, and works well, including and most especially
>     the historical access features.  I've already fallen in love with being
>     able to create a softlink to a '@@0x<timestamp>' string to access
>     snapshots.

As long as I'm asking HAMMER-related questions... This may be obvious from the 
code but I haven't looked at it yet. Will it be possible to disable the 
historical access feature and still have the possibility to take a snapshot 
(of the filesystem or a directory tree) at some point in time?

Thanks,
Aggelos