VERY slow Testlink- Performance issue

[MP]

I have testlink installed on a VERY POWERFUL server ( I don't have the
config details, but it's powerful machine with 16gig ram, quad core
dual CPU, etc), but with just 500 test cases in a test plan, the
performance is very slow, it takes 30-40 sec to see the tree of test
cases in Execute tab. Testlink pilot is going on with a small team and
I think, it will be an issue for a big team (~10,000 test cases).
Please let me know if there is any performance tuning parameter to get
the better performance.

Rgds,
MP

[Kevin Levy]

Shouldn't we make JTREE be the default?

Kevin

---

> Date: Mon, 17 Mar 2008 16:02:46 -0700
> Subject: [testlink-dev] VERY slow Testlink- Performance issue
> From: mpv...@gmail.com
> To: testli...@googlegroups.com

[Christian Murray]

We have the same performance issues, even using JTREE, and especially
on Firefox, and it gets worse with the number of executions of each
test case, especially if you have bug-tracking (we use bugzilla)
integration enabled -- because it queries your bug-tracker for each
failure displayed that has bug(s) associated with it.
Our workaround is to limit the number of test cases in a test plan to
about 100, which is okay -- that's a good number for one person to
manage anyway.
Generally, each tester owns one test plan, so I've also implemented a
wrapper object around test plans, so we can get meaningful reports
across multiple test plans.

[Francisco Mancardi]

1. Please send me a dump (zipped) of your db (francisco...@gmail.com)
2. explain better in what areas of tl you find performance problems

thanks
> Rgds,
> MP
> >
>

[Francisco Mancardi]

New idea I've implemented on CVS HEAD is:
IN EXECUTE MODE: do not show all testcases in a testsuite when you
click it on tree.
You can only access ONE TESTCASE at a time to execute it.

> >
>

[Joe23]

So does this mean you got rid of the bulk test case execution?

I can see not displaying all test cases of you click on the root of
the test plan, but not displaying them all when you click on
individual test suites removes the bulk test execution feature. That
removes a valuable feature that I use.

Joe

On Mar 18, 1:09 am, Francisco Mancardi

[MP]

We have bugzilla integrated too. If bugzilla is the cause of the perf
issue then should TL schedule the bugzilla query in the off time
(configurable), and maintain the status, and update it again if user
clicks on the bug,etc.

Maintaining many test plans will be problem for us as we haven't come
across any way to generate report for multiple test plans. The concept
of test plan ( we renamed to Test Release) works fine for us as long
as we don't face the performance issue.

Rgds,
MP

On Mar 17, 11:24 pm, Christian Murray <Christian.Mur...@gmail.com>
wrote: