Details
-
Type:
Improvement
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Infrastructure: CatTrack
-
Labels:None
-
Number of attachments :
Description
Currently we are serving cattrack using a single instance of mongrel. This serializes all access to the service which up until the current time has not been an issue as the server is not under a large load and none of the requests take too long to serve. As of r13810 the ability to query the output of test_case_executions was added and serving this request can take a long time. While that request is being served no other requests can be served which means the server can appear to hang.
We should serve the website with a cluster of mongrel instances so the website does not appear to be hung while running the queries. It should be a relatively easy configuration change (see [1] & [2]).
[1] http://mongrel.rubyforge.org/wiki/Apache
[2] http://mongrel.rubyforge.org/wiki/MongrelCluster
Issue Links
- is depended upon by
-
RVM-687
Cattrack performance: regression report unusable
-
Activity
Peter Donald
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description |
Currently we are serving cattrack using a single instance of mongrel. This serializes all access to the service which up until the current time has not been an issue as the server is not under a large load and none of the requests take too long to serve. As of r13810 the ability to query the output of test_case_executions was added and serving this request can take a long time. While that request is being served no other requests can be served which means the server can appear to hang. We should serve the website with a cluster of mongrel instances so the website does not appear to be hung while running the queries. It should be a relatively easy configuration change. |
Currently we are serving cattrack using a single instance of mongrel. This serializes all access to the service which up until the current time has not been an issue as the server is not under a large load and none of the requests take too long to serve. As of r13810 the ability to query the output of test_case_executions was added and serving this request can take a long time. While that request is being served no other requests can be served which means the server can appear to hang. We should serve the website with a cluster of mongrel instances so the website does not appear to be hung while running the queries. It should be a relatively easy configuration change (see [1]). [1] http://mongrel.rubyforge.org/docs/apache.html |
David Grove
made changes -
| Fix Version/s | 1000 [ 14184 ] |
Peter Donald
made changes -
Peter Donald
made changes -
| Description |
Currently we are serving cattrack using a single instance of mongrel. This serializes all access to the service which up until the current time has not been an issue as the server is not under a large load and none of the requests take too long to serve. As of r13810 the ability to query the output of test_case_executions was added and serving this request can take a long time. While that request is being served no other requests can be served which means the server can appear to hang. We should serve the website with a cluster of mongrel instances so the website does not appear to be hung while running the queries. It should be a relatively easy configuration change (see [1]). [1] http://mongrel.rubyforge.org/docs/apache.html |
Currently we are serving cattrack using a single instance of mongrel. This serializes all access to the service which up until the current time has not been an issue as the server is not under a large load and none of the requests take too long to serve. As of r13810 the ability to query the output of test_case_executions was added and serving this request can take a long time. While that request is being served no other requests can be served which means the server can appear to hang. We should serve the website with a cluster of mongrel instances so the website does not appear to be hung while running the queries. It should be a relatively easy configuration change (see [1] & [2]). [1] http://mongrel.rubyforge.org/wiki/Apache [2] http://mongrel.rubyforge.org/wiki/MongrelCluster |
David Grove
made changes -
| Assignee | David Grove [ dgrove ] |
David Grove
made changes -
| Fix Version/s | 3.2 [ 14379 ] | |
| Fix Version/s | 1000 [ 14184 ] |
David Grove
made changes -
| Status | Open [ 1 ] | Closed [ 6 ] |
| Resolution | Fixed [ 1 ] |
David Grove
made changes -
| Status | Closed [ 6 ] | Reopened [ 4 ] |
| Resolution | Fixed [ 1 ] |
David Grove
made changes -
| Fix Version/s | 3.2 [ 14379 ] |
David Grove
made changes -
| Status | Reopened [ 4 ] | Closed [ 6 ] |
| Resolution | Fixed [ 1 ] |
I've just finished doing this for the cattrack instance I'm running internally in watson for use by X10.
It was fairly easy, so at some point in the next month or two I'd like to try it for jikes rvm. As part of that, I'd also like to change
the deploy story over to using capistrano. I've got the basic setup for that in the branch I'm using for x10 development.