General performance of Testlink 1.7+

[havlatm]

Try to remove nifty feature. I guess this could work:
Modify cfg/const.php

Code: Select all

define('MENU_ITEM_OPEN', '<div class="menu_bubble">');

to

Code: Select all

define('MENU_ITEM_OPEN', '<div>');

We are aware about the problem. I'll add it into the 1.8 RC2 scope. Let us if it helps. Thanks.

[fman]

please get last 1.8 CVS code before doing your tests.

[fman]

you can not compare 1.0.4 performance with 1.8, because DB structure is
completely different.
To have N deep tree you have to pay on performance.

Surelly using test plans with 4000 test cases posses non a simple problem
because you need lot of memory to hold test plan data on memory.

[lshiva86]

Thank you very much for the suggestions. But even after making the change to avoid nifty, the performance has not improved much.

In Testlink 1.0.4 we had made the changes to facilitate n levels of test suites, quite some time back, but it is very fast. I dont understand how 1.7 and 1.8 are so slow. I am still studying that. If i find any progress I shall let you know. Thank you so much.

Meanwhile if you come to know any database tuning which can improve the performance, please let me know. Since the 1.7 and 1.8 versions have such advanced features and awesome UI , we are suggesting migration to 1.7 only for those who have testcases less than 2000 in a testplan. But we have a very large no of users using testlink. So I would be very grateful if you can help me out in this. Thanks again.

[alphaprime]

We are using TestLink 1.70 and are generally happy with the tool. As others have stated, there are performance issues when you have large amounts of data. We have 10,500+ test cases with a team of 10 QA Engineers actively updating and executing test cases all day long.

We did notice some improvement when we switched to JTree but my overall concern is that we will soon hit the wall on performance as we continue to add more test cases and test plans to TestLink.

My question to the TestLink Development team is how are these issues going to be addressed? Has anyone done any volume testing with over 100k test cases with 25 test plans and 100 users...

I'm part of a global QA team that is evaluating whether or not we should roll this tool out on a larger scale. We are almost hitting the wall with 10 QA Engineers so how will this tool scale if we have 100 QA Engineers?

[lshiva86]

http://www.teamst.org/phpBB2/viewtopic.php?t=1235