RTC/Jazz V2 Breaks when we go to 100 concurrent users
My immediate research group and I (~6 people) have been using Jazz/RTC (v2) almost "straight out of the box" without a hitch for over a year.
I decided to introduce this platform to an undergraduate class of 100 students at the University of Virginia. I added all 100 as users and ran 2 lab sessions of 50 students each in which students had to download RTC, connect to Jazz, set up a project, etc.
Jazz died almost instantly: as soon as some threshold was exceeded. The Jazz logs show Jazz getting a null JDBC connection. The DB2 logs on the other hand show no errors.
QUESTION: What set of Jazz and/or DB2 configuration parameters do we need to change, from their "out-of-the-box" values, to make this software work with up to 100 concurrent developers?
I posted this query one other place (CLM), and realize that this question could also have gone into the academic category, but it's really more about systems administration/configuration (technical stuff) than about teaching or research, so I put it here. Hope this is an okay place to ask this question.
Thanks,
Kevin Sullivan
sullivan@virginia.edu
I decided to introduce this platform to an undergraduate class of 100 students at the University of Virginia. I added all 100 as users and ran 2 lab sessions of 50 students each in which students had to download RTC, connect to Jazz, set up a project, etc.
Jazz died almost instantly: as soon as some threshold was exceeded. The Jazz logs show Jazz getting a null JDBC connection. The DB2 logs on the other hand show no errors.
QUESTION: What set of Jazz and/or DB2 configuration parameters do we need to change, from their "out-of-the-box" values, to make this software work with up to 100 concurrent developers?
I posted this query one other place (CLM), and realize that this question could also have gone into the academic category, but it's really more about systems administration/configuration (technical stuff) than about teaching or research, so I put it here. Hope this is an okay place to ask this question.
Thanks,
Kevin Sullivan
sullivan@virginia.edu
One answer
My immediate research group and I (~6 people) have been using Jazz/RTC (v2) almost "straight out of the box" without a hitch for over a year.
I decided to introduce this platform to an undergraduate class of 100 students at the University of Virginia. I added all 100 as users and ran 2 lab sessions of 50 students each in which students had to download RTC, connect to Jazz, set up a project, etc.
Jazz died almost instantly: as soon as some threshold was exceeded. The Jazz logs show Jazz getting a null JDBC connection. The DB2 logs on the other hand show no errors.
QUESTION: What set of Jazz and/or DB2 configuration parameters do we need to change, from their "out-of-the-box" values, to make this software work with up to 100 concurrent developers?
I posted this query one other place (CLM), and realize that this question could also have gone into the academic category, but it's really more about systems administration/configuration (technical stuff) than about teaching or research, so I put it here. Hope this is an okay place to ask this question.
Thanks,
Kevin Sullivan
sullivan@virginia.edu
Hi Kevin
100 concurrent users is a rather low number of users, so RTC should cope with that quite happily.
Can you give us some idea of your setup? What sort of OS are you running, what sort of HW (memory).
You may also want to look at the tuning guide for hints:
http://jazz.net/library/article/208
and here:
http://jazz.net/library/article/204
regards
anthony