Yes, steps (2, 4, 5) will take locks as you described. Any number of concurrent
requests could get to step #3 before the write locks have to be taken.
I believe URIs like {$id}-{$version} would be safe because any threads that
don't get the write locks will restart from the beginning, rather tha
Hi Michael,
Thanks for your reply. I guess I am still missing something as it is not clear
to me how encoding both the id and version into the file URI would help me? I
could understand if I was just encoding the id as that will not change over
time, however for each request we are potentially
For comparison,
I managed to reach up to 3000 inserts per sec on a single host with a single
forest, but I am running on SSD, and I wasn't using MLCP transforms, nor
anything else that could touch the content between read from disk and insert
into database. I likely hadn't any range indexes enable
Hi all,
I am trying to tune one of the module in Marklogic.
I am using cts:values with path-range-indexes and it is taking more time
when compared to cts:element-values with element-range-indexes.
So my question is which combination is better to go with?
1. cts:values + path-range-indexes
2.
