Adding infinispan dev and Martin.
I think it makes a lot of sense for QE to run the tests you suggested.
Sent from my iPhone
On 30 Jul 2013, at 17:56, Shane Johnson <shjohnso(a)redhat.com> wrote:
I was looking at the code for this cache store the other day.
I noticed that is neither a log structured nor a b/b+ tree implementation and it lacks
compaction. Maybe it is elsewhere or I simply missed it?
Have we run a long test (as in hours) with variable length values? It looks like this
implementation may be inefficient in that it would result in numerous gaps (unusable free
entries) if the values grow or shrink in size. Where the tests run on SSD drives? I'd
think that this type of random read/write would not be terribly efficient on an HDD.
Have we done performance testing using FileDescriptor.sync() and have we considered using
an AsynchronousFileChannel instead?
Thanks,
Shane