db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6533) Add a quiet mode to NsTest
Date Mon, 28 Apr 2014 20:04:15 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983474#comment-13983474

Rick Hillegas commented on DERBY-6533:

I ran NsTest for 6 hours on the 8 core machine, using an engine to which I'd applied the derby-6542-02-ab-useNewSequenceGenerator.diff
patch. No errors. No timeouts. Here is the output:

	Number of INSERTS = 1769433
	Number of UPDATES = 871363
	Number of DELETES = 872081
	Number of SELECTS = 77837

	Number of failed INSERTS = 0
	Number of failed UPDATES = 847195
	Number of failed DELETES = 847304
	Number of failed SELECTS = 0

  Note that this may not be the same as the server side connections made
   to the database especially if connection pooling is employed

NOTE: Failing operations could be because of locking issue that are
directly related to the application logic.  They are not necessarily bugs.

Max sequence counter peeked at = 1804792

Last total memory = 6329204736, last free memory = 4301127624 as measured at Mon Apr 28 21:36:34
CEST 2014

> Add a quiet mode to NsTest
> --------------------------
>                 Key: DERBY-6533
>                 URL: https://issues.apache.org/jira/browse/DERBY-6533
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions:
>            Reporter: Rick Hillegas
>            Assignee: Rick Hillegas
>         Attachments: derby-6533-01-aa-quietMode.diff, derby-6533-02-aa-sequencesAndMoreStats.diff,
derby-6533-02-aa-sequencesAndMoreStats.out, derby-6533-03-timerThread.diff, derby-6533-04-outOfMemory.diff,
derby-6533-05-aa-dieQuickly.diff, derby-6533-07-aa-moreDefensiveCode.diff, derby-6533-08-aa-sortErrors.diff,
derby-6533-aa-anotherNPE.diff, nstest.out, nstest.out, nstest.out, nstest.out, nstest.out,
nstest.out, nstest.out, nstest.out, nstest.out
> Right now NsTest produces an enormous log file. This may be useful for tracking down
some errors. However, this can also make it hard to find the signal in the noise. It would
be good to turn off the chatty diagnostics which report the result of every insert, update,
delete, and select. A summary at the end may be good enough, including a summary of the number
of times each kind of error (SQLState) was seen. While I'm in there, I plan to make other
smallish changes.

This message was sent by Atlassian JIRA

View raw message