You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Ramandeep Kaur <ra...@yngvi.org> on 2005/03/15 22:25:31 UTC

Using DOTS as Derby System Test

Hi,

Database Open Source Test Suite (DOTS) is a test suite designed for 
stress testing on database systems. Apache Derby was tested with DOTS to 
investigate its usefulness as a system test. After several iterations of 
the test, it was found that DOTS may provide some value to Derby as a 
system test. I have written a document to provide information to the 
Derby community regarding the use of DOTS as a system test suite.  I am 
attaching the document to this message.

Thanks,
Raman
(ramank@yngvi.org)





Re: Using DOTS as Derby System Test

Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Ramandeep Kaur wrote:
> Database Open Source Test Suite (DOTS) is a test suite designed for 
> stress testing on database systems. Apache Derby was tested with DOTS to 
> investigate its usefulness as a system test. After several iterations of 
> the test, it was found that DOTS may provide some value to Derby as a 
> system test. I have written a document to provide information to the 
> Derby community regarding the use of DOTS as a system test suite.  I am 
> attaching the document to this message.

It's added to the web site site. Thanks for the contribution.

  -jean



Re: Using DOTS as Derby System Test

Posted by Jack Klebanoff <kl...@sbcglobal.net>.
Ramandeep Kaur wrote:

> Hi,
>
> Database Open Source Test Suite (DOTS) is a test suite designed for 
> stress testing on database systems. Apache Derby was tested with DOTS 
> to investigate its usefulness as a system test. After several 
> iterations of the test, it was found that DOTS may provide some value 
> to Derby as a system test. I have written a document to provide 
> information to the Derby community regarding the use of DOTS as a 
> system test suite.  I am attaching the document to this message.
>
> Thanks,
> Raman
> (ramank@yngvi.org)
>
In her attached PDF file Ramandeep wrote "the jvm memory size will 
depend on how long the test cases will be executed for". This sounds 
like Derby has a memory leak, which is a real problem. The memory usage 
should quickly rise to a peak and then level off, unless the test driver 
has a memory leak itself, or it steadily increases the number of open 
connections, PreparedStatements, etc.

Jack Klebanoff