Comments on: Using Terracotta To Cluster a Single JVM Master/Worker Application http://abramsm.wordpress.com/2007/10/05/using-terracotta-to-cluster-an-single-jvm-masterworker-application/ yet another Java development blog Sun, 20 Jul 2008 17:33:09 +0000 http://wordpress.org/?v=MU By: Bob http://abramsm.wordpress.com/2007/10/05/using-terracotta-to-cluster-an-single-jvm-masterworker-application/#comment-15 Bob Wed, 28 Nov 2007 16:01:37 +0000 http://abramsm.wordpress.com/2007/10/05/using-terracotta-to-cluster-an-single-jvm-masterworker-application/#comment-15 Hello, I'm researching a topic (JVM) and came to your site to read about instrumenting code (google search). My experience with instrumenting code has been in QA which is what I do. For example, McCabe Tools: comprehensive test / code coverage to focus, monitor, and document software testing processes assesses the thoroughness of your testing and aids in gauging the time and resources needed to ensure a well-tested application. My question is: how does instrumenting differ in the developer world? I've seen this to often now, and need to know. Thanks. Hello,
I’m researching a topic (JVM) and came to your site to read about instrumenting code (google search).

My experience with instrumenting code has been in QA which is what I do.

For example, McCabe Tools:

comprehensive test / code coverage to focus, monitor, and document software testing processes

assesses the thoroughness of your testing and aids in gauging the time and resources needed to ensure a well-tested application.

My question is: how does instrumenting differ in the developer world?
I’ve seen this to often now, and need to know. Thanks.

]]> By: Classiest Posts about Java (10-12-2007) | spokedweb.com http://abramsm.wordpress.com/2007/10/05/using-terracotta-to-cluster-an-single-jvm-masterworker-application/#comment-5 Classiest Posts about Java (10-12-2007) | spokedweb.com Fri, 12 Oct 2007 14:49:21 +0000 http://abramsm.wordpress.com/2007/10/05/using-terracotta-to-cluster-an-single-jvm-masterworker-application/#comment-5 [...] have a gander at Using Terracotta to Cluster a Single JVM Master/Worker Application.  This post is a nice demonstration of taking a batch processing framework and quickly clustering [...] [...] have a gander at Using Terracotta to Cluster a Single JVM Master/Worker Application.  This post is a nice demonstration of taking a batch processing framework and quickly clustering [...]

]]> By: abramsm http://abramsm.wordpress.com/2007/10/05/using-terracotta-to-cluster-an-single-jvm-masterworker-application/#comment-3 abramsm Fri, 05 Oct 2007 11:13:25 +0000 http://abramsm.wordpress.com/2007/10/05/using-terracotta-to-cluster-an-single-jvm-masterworker-application/#comment-3 Jonas - Thanks for your comment and all your work on Terracotta. I will check out the WorkManager implementation ASAP. Regards, Matt Jonas -

Thanks for your comment and all your work on Terracotta. I will check out the WorkManager implementation ASAP.

Regards,
Matt

]]> By: Jonas Bonér http://abramsm.wordpress.com/2007/10/05/using-terracotta-to-cluster-an-single-jvm-masterworker-application/#comment-2 Jonas Bonér Fri, 05 Oct 2007 10:05:41 +0000 http://abramsm.wordpress.com/2007/10/05/using-terracotta-to-cluster-an-single-jvm-masterworker-application/#comment-2 Hi there. Great post. I am really glad to see that you are having good experiences in exploring the power and simplicity of Terracotta. Just a note, the blog article that you are referring to (as well as the forge project 'open data grid' - which is the implementation of the concepts behind the article) is optimized for simplicity and understandability, with the main objective to explain the concepts behind using Terracotta and the Master/Worker pattern to implement work load management. We have another implementation which is optimized for scale and performance (however a bit harder to understand). It adds the concepts of in and outgoing channels, batching channels etc., all in order to maximize locality of reference and minimizing contention. Its is build on the same concepts and set of interfaces (CommonJ). You can find that implementation here: http://terracotta.org/confluence/display/labs/WorkManager Regards, Jonas. Hi there.

Great post. I am really glad to see that you are having good experiences in exploring the power and simplicity of Terracotta.

Just a note, the blog article that you are referring to (as well as the forge project ‘open data grid’ - which is the implementation of the concepts behind the article) is optimized for simplicity and understandability, with the main objective to explain the concepts behind using Terracotta and the Master/Worker pattern to implement work load management.

We have another implementation which is optimized for scale and performance (however a bit harder to understand). It adds the concepts of in and outgoing channels, batching channels etc., all in order to maximize locality of reference and minimizing contention. Its is build on the same concepts and set of interfaces (CommonJ). You can find that implementation here:
http://terracotta.org/confluence/display/labs/WorkManager

Regards, Jonas.

]]>