On 2/4/12 5:53 PM, Manik Surtani wrote:
On 2 Feb 2012, at 07:53, Bela Ban wrote:
I can also reproduce it by now, in JGroups: I simply create 12 members
in a loop...
Don't need the bombastic Transactional test
Yup; Transactional was made to benchmark and profile 2-phase transactions -
Apologies for being so late on this thread.
On 1 Feb 2012, at 18:12, Sanne Grinovero wrote:
On 1 February 2012 16:40, Bela Ban b...@redhat.com wrote:
Your benchmark is giving me the creeps !
Manik was the original author, I've only been adapting it slightly to
identify performance issues.
On 2 Feb 2012, at 07:53, Bela Ban wrote:
I can also reproduce it by now, in JGroups: I simply create 12 members
in a loop...
Don't need the bombastic Transactional test
Yup; Transactional was made to benchmark and profile 2-phase transactions - as
the name suggests! ;) - in Infinispan.
On Wed, Feb 1, 2012 at 9:48 AM, Bela Ban b...@redhat.com wrote:
On 1/31/12 10:55 PM, Dan Berindei wrote:
Hi Bela
I guess it's pretty clear now... In Sanne's thread dump the main
thread is blocked in a cache.put() call after the cluster has
supposedly already formed:
On 1 February 2012 15:18, Bela Ban b...@redhat.com wrote:
On 2/1/12 10:25 AM, Dan Berindei wrote:
That's not the way it works; at startup of F, it sends its IP address
with the discovery request. Everybody returns its IP address with the
discovery response, so even though we have F only
Your benchmark is giving me the creeps !
First, which version of JGroups / Infinispan does this use ? Second, is
there a way to start this in an IDE rather than through maven ? Third, I
don't think bench-jgroups.xml is picked up at all ! How do I make a
change to bench-jgroups.xml and have
On 1 February 2012 16:40, Bela Ban b...@redhat.com wrote:
Your benchmark is giving me the creeps !
Manik was the original author, I've only been adapting it slightly to
identify performance issues. I wouldn't have used Maven either, but
it's serving me well especially since it turns out I have
Hi Bela
I think I found why you weren't seeing the warnings. The
bench-log4j.xml in github master is configured to log only to the log
file (benchmark.log). If you add an appender-ref ref=CONSOLE/
you'll see the warnings on the console as well.
I am now able to reproduce it pretty reliably, even
I can also reproduce it by now, in JGroups: I simply create 12 members
in a loop...
Don't need the bombastic Transactional test
Looking into it.
On 2/2/12 7:46 AM, Dan Berindei wrote:
Hi Bela
I think I found why you weren't seeing the warnings. The
bench-log4j.xml in github master is
I have sporadically seen this before when running some perf tests as well …
curious to know what's up.
On 30 Jan 2012, at 17:45, Sanne Grinovero wrote:
Hi Bela,
this is the same error we where having in Boston when preparing the
Infinispan nodes for some of the demos. So I didn't see it for
Hi Bela
I guess it's pretty clear now... In Sanne's thread dump the main
thread is blocked in a cache.put() call after the cluster has
supposedly already formed:
org.infinispan.benchmark.Transactional.main() prio=10
tid=0x7ff4045de000 nid=0x7c92 in Object.wait()
[0x7ff40919d000]
On 1/31/12 10:55 PM, Dan Berindei wrote:
Hi Bela
I guess it's pretty clear now... In Sanne's thread dump the main
thread is blocked in a cache.put() call after the cluster has
supposedly already formed:
org.infinispan.benchmark.Transactional.main() prio=10
tid=0x7ff4045de000
12 matches
Mail list logo
