correctness can be achieved in many different ways, synchronization
just happens to be the easiest one.
The build is working, including session replication (modules
groupcom,ha,storeconfig-ha), just uncomment one line in
container/modules/build.properties and tomcat builds the new modules
inst
I agree, heartbeat is not that important w.r.t. performance. I used it
as a simple test for how DTrace will be able to help. And at least in
that nearly trivial test case the results are already interesting.
Another thing that DTrace can check is lock contention. So there's more
to come :)
D
Cool Rainer, interesting numbers. Can you run the same numbers on the
new module groupcom.
I have done some optimizations there, for example, the name isn't
broadcasted. And I am about to remove the domain, instead of having a
default one. also, I agree, lets not translate the 4byte IP and the
Hi,
I started to trace TC cluster with DTrace. I did a first simple exam for
the mcast subcomplex. CPU usage and especially elapsed times might be
slightly larger than expected, because I used the more intrusive
extended DTrace probes.
All tests were done with JDK 1.6.0 build 72 on Solaris 10 SP
