Collated: Fault-Free
Instructions
To obtain these results, follow all instructions for the Round Trip measurements, but use the special time-capture UserProfileSessionBean.java in the build. Further, everything in the special Bean points to use while logged in as ksteppe.
Results
Server Side Top Info:
· Top before (col_ff_before_top_drlucky.txt)
· Top after (col_ff_after_top_drlucky.txt)
Comparison of times. Please note that in order to not overload the results, these tests were taken at different times, and so the data, although we did multiple tests, came out much differently than expected.
Compare the above Top info against the round trip top info:
RoundTrip:
· Top before (col_ff_before_top_drlucky.txt)
· Top after (col_ff_after_top_drlucky.txt)
Distributed: Fault Free
Instructions
See above.
Results
Server Side:
· Top before - drlucky (distrib_ff_before_top_drlucky.txt)
· Top after - drlucky (distrib_ff_after_top_drlucky.txt)
· Top before - scrabble (distrib_ff_before_top_scrabble.txt)
· Top after - scrabble (distrib_ff_after_top_scrabble.txt)
· Top before - client (distrib_ff_before_top_client.txt)
· Top after - client (distrib_ff_after_top_client.txt)
Round Trip:
· Top before - drlucky (distrib_ff_before_top_drlucky.txt)
· Top after - drlucky (distrib_ff_after_top_drlucky.txt)
· Top before - risk (distrib_ff_before_top_risk.txt)
· Top after - risk (distrib_ff_after_top_risk.txt)
· Top before - client (distrib_ff_before_top_client.txt)
· Top after - client (distrib_ff_after_top_client.txt)
Distributed: With Faults
These tests did not make much sense to get into on the server side, as in general the overall time for invocations between the server and the "sacred" machine were independent of failovers.