Hmm, looking into this. Thanks Ales!
On 13-01-03 9:32 PM, Ales Justin wrote:
@Vladimir: any idea why the NPE?
OpenShift only, it occurs on a sequence of requests with no delay between
them.
Matej.
On 03/01/13 20:58, Ales Justin wrote:
Can you reproduce this locally?
Or OpenShift
Hi,
I have created a comparison how JDG (library mode) behaves depending on the
contention on keys. The test runs standard (20% puts, 80% gets) stress test on
different amount of keys (while there are always 80k keys loaded into the
cache) with 10 concurrent threads on each of 8 nodes, for 10
Ales,
I am totally puzzled how is this possible, never seen it before. In
order for DefaultExecutorService to fail on line 950 with NPE, the
underlying Future field of DistributedTaskPart has to be set to null.
Future field is set only in two places, if task is executed locally [1]
or
|
| As for the low contention cases, I think they're all about the same
| as the probability for contention is all very low given the number
| of threads used. Perhaps if these were cranked up to maybe 50 or 100
| threads, you'd see a bigger difference?
Right, I think that there should be no
Very interesting results, and thanks Mircea to implement the new pattern!
The effect on near-CPU caches is an interesting hypothesis, it would
be nice to measure it; if you happen to run them again, could you use
perf ?
Last time I had run it - almost a year ago - the counters had shown
very
| The effect on near-CPU caches is an interesting hypothesis, it would
| be nice to measure it; if you happen to run them again, could you use
| perf ?
| Last time I had run it - almost a year ago - the counters had shown
| very large opportunities for improvements (a nice way to say it was a
|
On 4 January 2013 17:10, Radim Vansa rva...@redhat.com wrote:
| The effect on near-CPU caches is an interesting hypothesis, it would
| be nice to measure it; if you happen to run them again, could you use
| perf ?
| Last time I had run it - almost a year ago - the counters had shown
| very
Hi guys
We haven't managed to get all the blockers in, so we've moved the CR1
release date again: Tuesday, Jan 8th.
Cheers,
Dan
On Dec 18, 2012 8:31 PM, Mircea Markus mmar...@redhat.com wrote:
Hi,
Next Infinispan release(5.2.0.CR1) is scheduled for Friday 21 Dec.
We still have 19 issues
