Huge testlink case pool and MySQL tunig

[narsu]

Hello!


I would like to know some good advises to tune MySQL database to serve testlink 1.9.4/5

There is one quite huge project with >8000 cases. Now I would like to tune little bit MySQL server speed (This database is running currently 1.9.3)
Also there is several project also in same database
I am going to use XAMPP package in Windows with huge_my.cfg. Is it wise at all?
Should I install pure MySQL server ? Is there any sense to change engine in MySQL ?
Please throw some ideas?

What I should check first?


PS. How much could be estimated performance difference between 1.9.3 and 1.9.5 in database handling

[fman]

Doing search on forum for 'Performance ' provide this

http://www.teamst.org/forum/viewtopic.p ... c06#p17094

One of our worst nightmare was tree building and rendering.
The use of results.class.php was one of the reason, because this class followed the wrong rule '...do more that what is needed ...'.
Due to tree nature of TestLink items, and the approach used to represent it on DB (the simple approach of nodes with parent and child),
we need to use methods with recursive calls, and surely this do not help on performance when you talk of thousands test cases and test suites.
Test plan are build using links, this means again tree walking backwards (from leaf to root) in order to build test plan tree for navigation.

All these factors affects performance. Due to lack of resources (people,hardware, realistic sample date, time) we are not able to do any kind of deep benchmarking when changing approach from one version to other.

It would be great i community can help with this kind of work