It's all about the answers!

Ask a question

RQM Performance


Sanal Menon (611612) | asked Sep 03 '09, 3:21 p.m.
We have noticed that after loading Requirements and Test cases into RQM, the performance has degraded significantly.
Total Requirements - 160
Total Test cases - 700

Any specific settings, tuning that cen be done to make it more performant?

Specific observations:
- Dynamic search on the Requirements / Test Cases search box seems to be taking up too much band width.

No attachments to any artifacts so far.

7 answers



permanent link
John Nason (2.4k1012) | answered Sep 03 '09, 5:56 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Hi Sanal,
First off, I hope you are using RQM2.0. Significant performance improvements have been made in 2.0.

Use the "View Builder" to narrow results by key attributes. In "Preferences" edit the View Builder settings to make these views open faster by default.

As an ADMIN user, go to Admin->System Properties->Artifact Options to lower your search threshold.

"Filter text" is client-side only on the results that are currently being displayed. Less results = faster search. View Builders (above) can aid in this. Also, since it is client-side only there should be no bandwith impact.

Hope that helps.
John

We have noticed that after loading Requirements and Test cases into RQM, the performance has degraded significantly.
Total Requirements - 160
Total Test cases - 700

Any specific settings, tuning that cen be done to make it more performant?

Specific observations:
- Dynamic search on the Requirements / Test Cases search box seems to be taking up too much band width.

No attachments to any artifacts so far.

permanent link
Sanal Menon (611612) | answered Sep 04 '09, 11:53 a.m.
Thanks for the reply.

Installation details:
RQM version = 2.0
IE version = 7 (Firefox cannot be used since it is not allowed by the client).
DB = Oracle
App server = Tomcat 5.5.23
Note: App and DB are on two separate physical servers.

I did the mentioned settings already. The problem with reducing the search threshold is that after the data is displayed, when you search for artifacts from the filter text, only those already displayed in the view are searched (for example, first 100 records).

So the performance issue is still existing.

The performance problem I see are during hte following operations.
1. Saving a Test Case / Requrement
2. Searching for artifacts using the "Filter Text" box.
3. Searching (/displaying) test cases on the view.
4. On linking requirements to a test case (Requirements section with in the test case), when searching for requirements from the list.

The above have made the usage of RQM tremendous slow and really affecting productivity and users experience with RQM.

What could be done to fix this?

Thanks.

Hi Sanal,
First off, I hope you are using RQM2.0. Significant performance improvements have been made in 2.0.

Use the "View Builder" to narrow results by key attributes. In "Preferences" edit the View Builder settings to make these views open faster by default.

As an ADMIN user, go to Admin->System Properties->Artifact Options to lower your search threshold.

"Filter text" is client-side only on the results that are currently being displayed. Less results = faster search. View Builders (above) can aid in this. Also, since it is client-side only there should be no bandwith impact.

Hope that helps.
John

We have noticed that after loading Requirements and Test cases into RQM, the performance has degraded significantly.
Total Requirements - 160
Total Test cases - 700

Any specific settings, tuning that cen be done to make it more performant?

Specific observations:
- Dynamic search on the Requirements / Test Cases search box seems to be taking up too much band width.

No attachments to any artifacts so far.

permanent link
John Nason (2.4k1012) | answered Sep 10 '09, 3:18 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Thanks for the feedback, Sanal.
It is unfortunate that you need to use IE 7 since both IE 7 and 8 are much slower than Firefox.

Back to the filter text: can you use View Builder to narrow your results as a first step, then use the filter text to find the specific record? It sounds like we need to add more options to the view builder as well. What would you like to see?

I am forwarding this information along to our performance gurus.

Believe me, performance is still on our radar. No promises on specifics - but upcoming releases will continue to have more performance boosts.

Regards,
John

Thanks for the reply.

Installation details:
RQM version = 2.0
IE version = 7 (Firefox cannot be used since it is not allowed by the client).
DB = Oracle
App server = Tomcat 5.5.23
Note: App and DB are on two separate physical servers.

I did the mentioned settings already. The problem with reducing the search threshold is that after the data is displayed, when you search for artifacts from the filter text, only those already displayed in the view are searched (for example, first 100 records).

So the performance issue is still existing.

The performance problem I see are during hte following operations.
1. Saving a Test Case / Requrement
2. Searching for artifacts using the "Filter Text" box.
3. Searching (/displaying) test cases on the view.
4. On linking requirements to a test case (Requirements section with in the test case), when searching for requirements from the list.

The above have made the usage of RQM tremendous slow and really affecting productivity and users experience with RQM.

What could be done to fix this?

Thanks.

Hi Sanal,
First off, I hope you are using RQM2.0. Significant performance improvements have been made in 2.0.

Use the "View Builder" to narrow results by key attributes. In "Preferences" edit the View Builder settings to make these views open faster by default.

As an ADMIN user, go to Admin->System Properties->Artifact Options to lower your search threshold.

"Filter text" is client-side only on the results that are currently being displayed. Less results = faster search. View Builders (above) can aid in this. Also, since it is client-side only there should be no bandwith impact.

Hope that helps.
John

We have noticed that after loading Requirements and Test cases into RQM, the performance has degraded significantly.
Total Requirements - 160
Total Test cases - 700

Any specific settings, tuning that cen be done to make it more performant?

Specific observations:
- Dynamic search on the Requirements / Test Cases search box seems to be taking up too much band width.

No attachments to any artifacts so far.

permanent link
John Nason (2.4k1012) | answered Sep 11 '09, 4:11 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Sanal - I have one more suggestion that I completely forgot about in the last reply. Please look into our alternate views added in 2.0. We have new "Tree" and "Explorer" views that are much faster than the standard views.
Read about them here: http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/topic/com.ibm.rational.test.qm.doc/topics/t_change_search_results_view.html

Regards,
John


Thanks for the reply.

Installation details:
RQM version = 2.0
IE version = 7 (Firefox cannot be used since it is not allowed by the client).
DB = Oracle
App server = Tomcat 5.5.23
Note: App and DB are on two separate physical servers.

I did the mentioned settings already. The problem with reducing the search threshold is that after the data is displayed, when you search for artifacts from the filter text, only those already displayed in the view are searched (for example, first 100 records).

So the performance issue is still existing.

The performance problem I see are during hte following operations.
1. Saving a Test Case / Requrement
2. Searching for artifacts using the "Filter Text" box.
3. Searching (/displaying) test cases on the view.
4. On linking requirements to a test case (Requirements section with in the test case), when searching for requirements from the list.

The above have made the usage of RQM tremendous slow and really affecting productivity and users experience with RQM.

What could be done to fix this?

Thanks.

Hi Sanal,
First off, I hope you are using RQM2.0. Significant performance improvements have been made in 2.0.

Use the "View Builder" to narrow results by key attributes. In "Preferences" edit the View Builder settings to make these views open faster by default.

As an ADMIN user, go to Admin->System Properties->Artifact Options to lower your search threshold.

"Filter text" is client-side only on the results that are currently being displayed. Less results = faster search. View Builders (above) can aid in this. Also, since it is client-side only there should be no bandwith impact.

Hope that helps.
John

We have noticed that after loading Requirements and Test cases into RQM, the performance has degraded significantly.
Total Requirements - 160
Total Test cases - 700

Any specific settings, tuning that cen be done to make it more performant?

Specific observations:
- Dynamic search on the Requirements / Test Cases search box seems to be taking up too much band width.

No attachments to any artifacts so far.

permanent link
Jirong Hu (1.5k9295258) | answered Mar 06 '10, 9:47 p.m.
Hi John

I am going to take a new job where is having the same problem as only IE is allowed. One of your RQM practice lead just told me that the next RQM version maybe better.

Do you know when will this version be out?

Thanks
Jirong

Sanal - I have one more suggestion that I completely forgot about in the last reply. Please look into our alternate views added in 2.0. We have new "Tree" and "Explorer" views that are much faster than the standard views.
Read about them here: http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/topic/com.ibm.rational.test.qm.doc/topics/t_change_search_results_view.html

Regards,
John


Thanks for the reply.

Installation details:
RQM version = 2.0
IE version = 7 (Firefox cannot be used since it is not allowed by the client).
DB = Oracle
App server = Tomcat 5.5.23
Note: App and DB are on two separate physical servers.

I did the mentioned settings already. The problem with reducing the search threshold is that after the data is displayed, when you search for artifacts from the filter text, only those already displayed in the view are searched (for example, first 100 records).

So the performance issue is still existing.

The performance problem I see are during hte following operations.
1. Saving a Test Case / Requrement
2. Searching for artifacts using the "Filter Text" box.
3. Searching (/displaying) test cases on the view.
4. On linking requirements to a test case (Requirements section with in the test case), when searching for requirements from the list.

The above have made the usage of RQM tremendous slow and really affecting productivity and users experience with RQM.

What could be done to fix this?

Thanks.

Hi Sanal,
First off, I hope you are using RQM2.0. Significant performance improvements have been made in 2.0.

Use the "View Builder" to narrow results by key attributes. In "Preferences" edit the View Builder settings to make these views open faster by default.

As an ADMIN user, go to Admin->System Properties->Artifact Options to lower your search threshold.

"Filter text" is client-side only on the results that are currently being displayed. Less results = faster search. View Builders (above) can aid in this. Also, since it is client-side only there should be no bandwith impact.

Hope that helps.
John

We have noticed that after loading Requirements and Test cases into RQM, the performance has degraded significantly.
Total Requirements - 160
Total Test cases - 700

Any specific settings, tuning that cen be done to make it more performant?

Specific observations:
- Dynamic search on the Requirements / Test Cases search box seems to be taking up too much band width.

No attachments to any artifacts so far.

permanent link
John Nason (2.4k1012) | answered Mar 08 '10, 3:22 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
I think you're going to be very pleased with the performance improvements that were made in RQM 2.0.1. We've finally added serer side paging and it's a night and day difference.
I can't promise a specific date but RQM 2.0.1 should be out on/around March 19th.
Any feedback you have when you test it out would be appreciated. Preliminary feedback is very positive.
Regards,
John Nason

Hi John

I am going to take a new job where is having the same problem as only IE is allowed. One of your RQM practice lead just told me that the next RQM version maybe better.

Do you know when will this version be out?

Thanks
Jirong

Sanal - I have one more suggestion that I completely forgot about in the last reply. Please look into our alternate views added in 2.0. We have new "Tree" and "Explorer" views that are much faster than the standard views.
Read about them here: http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/topic/com.ibm.rational.test.qm.doc/topics/t_change_search_results_view.html

Regards,
John


Thanks for the reply.

Installation details:
RQM version = 2.0
IE version = 7 (Firefox cannot be used since it is not allowed by the client).
DB = Oracle
App server = Tomcat 5.5.23
Note: App and DB are on two separate physical servers.

I did the mentioned settings already. The problem with reducing the search threshold is that after the data is displayed, when you search for artifacts from the filter text, only those already displayed in the view are searched (for example, first 100 records).

So the performance issue is still existing.

The performance problem I see are during hte following operations.
1. Saving a Test Case / Requrement
2. Searching for artifacts using the "Filter Text" box.
3. Searching (/displaying) test cases on the view.
4. On linking requirements to a test case (Requirements section with in the test case), when searching for requirements from the list.

The above have made the usage of RQM tremendous slow and really affecting productivity and users experience with RQM.

What could be done to fix this?

Thanks.

Hi Sanal,
First off, I hope you are using RQM2.0. Significant performance improvements have been made in 2.0.

Use the "View Builder" to narrow results by key attributes. In "Preferences" edit the View Builder settings to make these views open faster by default.

As an ADMIN user, go to Admin->System Properties->Artifact Options to lower your search threshold.

"Filter text" is client-side only on the results that are currently being displayed. Less results = faster search. View Builders (above) can aid in this. Also, since it is client-side only there should be no bandwith impact.

Hope that helps.
John

We have noticed that after loading Requirements and Test cases into RQM, the performance has degraded significantly.
Total Requirements - 160
Total Test cases - 700

Any specific settings, tuning that cen be done to make it more performant?

Specific observations:
- Dynamic search on the Requirements / Test Cases search box seems to be taking up too much band width.

No attachments to any artifacts so far.

permanent link
David Mehaffy (90123338) | answered Mar 08 '10, 3:38 p.m.
JAZZ DEVELOPER
jnason wrote:
I think you're going to be very pleased with the performance
improvements that were made in RQM 2.0.1. We've finally added serer
side paging and it's a night and day difference.
I can't promise a specific date but RQM 2.0.1 should be out on/around
March 19th.
Any feedback you have when you test it out would be appreciated.
Preliminary feedback is very positive.
Regards,
John Nason

hujirongwrote:
Hi John
I am going to take a new job where is having the same problem as
only IE is allowed. One of your RQM practice lead just told me that
the next RQM version maybe better.
Do you know when will this version be out?

Thanks
Jirong

jnasonwrote:
Sanal - I have one more suggestion that I completely forgot about in
the last reply. Please look into our alternate views added in 2.0. We
have new "Tree" and "Explorer" views that are much
faster than the standard views.
Read about them here:
http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/topic/com.ibm.rational.test.qm.doc/topics/t_change_search_results_view.html
Regards,
John


sanalmenonwrote:
Thanks for the reply.
Installation details:
RQM version = 2.0
IE version = 7 (Firefox cannot be used since it is not allowed by
the client).
DB = Oracle
App server = Tomcat 5.5.23
Note: App and DB are on two separate physical servers.

I did the mentioned settings already. The problem with reducing the
search threshold is that after the data is displayed, when you search
for artifacts from the filter text, only those already displayed in
the view are searched (for example, first 100 records).
So the performance issue is still existing.

The performance problem I see are during hte following operations.
1. Saving a Test Case / Requrement
2. Searching for artifacts using the "Filter Text" box.
3. Searching (/displaying) test cases on the view.
4. On linking requirements to a test case (Requirements section with
in the test case), when searching for requirements from the list.
The above have made the usage of RQM tremendous slow and really
affecting productivity and users experience with RQM.
What could be done to fix this?

Thanks.

jnasonwrote:
Hi Sanal,
First off, I hope you are using RQM2.0.
Significant performance improvements
have been made in 2.0.
Use the "View Builder" to narrow results by key
attributes. In "Preferences" edit the View Builder settings
to make these views open faster by default.
As an ADMIN user, go to Admin->System Properties->Artifact
Options to lower your search threshold.
"Filter text" is client-side only on the results that are
currently being displayed. Less results = faster search. View
Builders (above) can aid in this. Also, since it is client-side only
there should be no bandwith impact.
Hope that helps.
John

sanalmenonwrote:
We have noticed that after loading Requirements and Test cases into
RQM, the performance has degraded significantly.
Total Requirements - 160
Total Test cases - 700

Any specific settings, tuning that cen be done to make it more
performant?
Specific observations:
- Dynamic search on the Requirements / Test Cases search box seems
to be taking up too much band width.
No attachments to any artifacts so
far.


I will second that - the performance is excellent in our pre-testing
with 2.0.1

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.