General performance of Testlink 1.7+

marty · Post by **marty** » Fri Jan 25, 2008 9:05 pm

Hello,

Is it possible to get some feedback from any of you about the usage you do of Testlink 1.7+

Example:

- # of Testcases
- # of Testprojects
- # of Testplans
- # of Users in Testlink
- # of concurrent users accessing Testlink
ect..

Do it perform well for you?

This would be very usefull for us and any future users of Testlink.
Thank you in Advance,

Martin

targetsmart · Post by **targetsmart** » Mon Feb 11, 2008 4:12 pm

- 1548 Testcases
- 1 Testproject
- 5 Testplans
- 21 Users in Testlink
- 13 concurrent users accessing Testlink

There is no problem with performance. It is satisfactory.

marty · Post by **marty** » Tue Feb 12, 2008 6:03 pm

Thank you very much for the feedback

Anyone else?

jbermejo · Post by **jbermejo** » Wed Feb 13, 2008 10:09 am

I had a project with more than than 3000 test cases; however, I had to change the $g_tree_type variable in config.inc.pho from 'LAYERSMENU' to 'JTREE' because it took more than 30 seconds to render the testcase tree when accessing the TL application from a remote dsl/vpn connection.

Nogem · Post by **Nogem** » Mon Feb 18, 2008 6:04 pm

- 260 of Testcases (so far and growing daily)
- 4 Testprojects
- 5 Testplans
- 15 Users in Testlink
- typically 5 concurrent users accessing Testlink

Our documented test cases are being expanded as constantly and consistently as time will allow. So far it holds up very well. We have noticed some caching issues with reporting, but otherwise are good with it so far.

A few things that we've noticed which might be great value adds for us:

- Test case linking within a given project/plan. Many tests may share steps. It would be a huge time saver if those steps could exist as one test and be linked to within the steps of tests that use them. Then we could have only one location to maintain.
- A simple automation friendly API: note that I have not explored the current API and need to upgrade our TL implementation as soon as time allows proving the ability to do so cleanly. This may already be present.
- The ability to regroup/renumber test cases in a manner which makes sense to a human from a reporting perspective. The automatically generated numbers become fairly arbitrary as test cases are added to existing suites.

That said, great product. I enjoy using compared to a couple 'enterprise' level TCM solutions I've been exposed to - and the support response in this community exceeds that of the afore mentioned exposures too. (Those exposures were forced on me and not enjoyed. Seriously, somebody should be prosecuted. They were totally uncalled for.)

Post by **havlatm** » Thu Feb 21, 2008 12:44 pm

I have about 3000 Test Cases in 6 projects. I know that users have 7000 and more Test Cases.
The bottleneck is tree menu. You should switch to JTREE component to get fast rendering of GUI. This component is fast enough for work with larger amounts.

Nogem · Post by **Nogem** » Thu Feb 21, 2008 8:58 pm

One of our testers just noted a decrease in responsiveness when he is using FireFox 2.0.0.12 as compared to IE7.

marty · Post by **marty** » Tue Feb 26, 2008 7:38 pm

Thank you very much for the responses.

I am pretty confident about the performance and yes I already switched to JTRee a long time ago

We might run a stress run using Loadrunner in April. I will certainly share the results over here if this happens.

Martin

lshiva86 · Post by **lshiva86** » Thu Sep 25, 2008 10:40 am

Hi I am evaluating Testlink 1.7 for Symphony Services. I have uploaded 2000 test cases. The time taken for rendering the tree was long. Now I have made the change from LAYERSMENU to JREE. Now when i click on the main test suite containing 2000 test cases, it takes a very long time(30 secs) to render the gui on the right hand side in execution page. Can any body please suggest me something? When i was using LAYERSMENU error in nifty script was coming. Now it doesnt come but the UI rendering on the right hand side of the execution page is very slow. Please suggest something.

Post by **fman** » Thu Sep 25, 2008 2:34 pm

1. switch to 1.8 , you can choose ajax tree
2. increase memory limit in php.ini

4000 or more test cases on one testplan will cause performance problems

aksinghv · Post by **aksinghv** » Fri Sep 26, 2008 4:19 am

Can you guide how to set the Ajax tree (which all are ajax tree) and recommended setting for momory in the php.ini?

This will guide others to better the performance of their TL installation.

svanuitert · Post by **svanuitert** » Fri Sep 26, 2008 4:19 pm

We currently have:
- 6 Active Test Projects
- 3 inactive Test Projects
- 5 Test Projects have an average of 1000 test cases
- 4 Test Projects have an average of 3600-3900 test cases

I have increased the memory limit to 256M in PHP and the execution and input timeouts to 180 seconds. We still get major performance problems during the execution of the test cases. In particular, when selecting a test suite from the JTREE menu will take up to 2 minutes to list the test cases. I am seeing the httpd thread at 99-100% cpu during this time. When I see the timeouts in the error log, the problem is in the ADODB layer of the software in the &_Execute function.

Question: Is there more tuning I can do with Apache2/PHP5 to resolve the execution issues, or should I begin the switch to TestLink 1.8 to solve the problem?

Thanks,
Scot Van Uitert
Control4, Inc.

[/list]

Post by **fman** » Fri Sep 26, 2008 4:28 pm

is possible to have your db to do tests ?
if yes send it to francisco.mancardi@gmail.com in zipped format

svanuitert · Post by **svanuitert** » Fri Sep 26, 2008 9:45 pm

The file should be in your email.

Thanks,
Scot

lshiva86 · Post by **lshiva86** » Mon Oct 06, 2008 11:59 am

fman wrote:1. switch to 1.8 , you can choose ajax tree
2. increase memory limit in php.ini

4000 or more test cases on one testplan will cause performance problems

Hi fman,

I tried both options you suggested.
1)I increased the memory limit in php.ini. This did not have much effect.
2)I installed Testlink 1.8 and tree used is EXTJS

In Testlink 1.7.4,
The tree builds up very fast even with 8000 test cases. But in the execution page the UI rendering of even 1000 test cases is so slow and it hangs. I included code to get them in pages. This works fine till 5000 test cases but after that even this fails.

In Testlink 1.8,

Importing 1000 test cases, Adding 1000 test cases to testplan and getting them on the UI for execution. All these are taking a very long time and it hangs after a while.

In both the versions after some time, in the execution page, an alert saying 'nifty.js is taking a long time and whether you would like to stop it' comes.

Please suggest something to improve the speed of Testlink. We have groups having 3000 test cases and these delays will affect us a lot. We were using Testlink 1.0.4 for 2 years and the performance was very fast. Can you please tell me some ways to bring in the same performance even in these versions?