On 2/20/06, John Embretsen <[EMAIL PROTECTED]> wrote:
> > I think it would be good to do a long running test with patch4+patch5 
> > before committing them. I'll be running the repro derbyStress.java with 1M 
> > prepared statements and will check client and server memory usage. Other 
> > than that, it may be good to run the patch through DOTS test. I do not have 
> > the DOTS setup. I would appreciate if John or anyone else has the setup for 
> > DOTS and will be willing to run the tests after I upload the new patches. 
> > Anyone has suggestions for other tests I can run to test this?
>
> I can run a DOTS test with patches 4 and 5 applied to the trunk,
> although it might take a few days until you see the results (since, well, the
> test is long-running, and I have limited machine resources at my disposal).
> I'll wait until the patches are ready, of course...
>
> Setting up a DOTS test is not a huge ordeal, though. I think you will be able
> to set it up as long as you have access to a linux machine and read the
> related documents at http://db.apache.org/derby/integrate/index.html.
>
> My particular set-up did not stray too far from the DOTS defaults (I can post
> the config file if you need it) - I think that as long as you use a similar
> heap size (I used 128 MB fixed heap, 64 MB fixed PermSpace) , you will get
> roughly the same results.

Thanks John. I'll also try to see if I can get a machine to setup DOTS
after I finish my current iteration of the patch.

Thanks,
Deepa

Reply via email to