Hi,
For TarMK, none of this is an issue as TarMK is all in memory on 1 JVM with
local disk. Scaling up by throwing RAM and IO at the problem is a viable
option, as far as it's safe/sensible to do so. But TarMK doesn't cluster,
and if it did cluster, this would probably be an issue.
I think, but co
Would add one more
4. Write throughput degradation - For non unique property index which
make use of ContentMirrorStoreStrategy we have seen a loss in
throughput due to contention which arise due to conflicts while
entries are made in index. (OAK-2673, OAK-3380)
Chetan Mehrotra
On Fri, Aug 5,
