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, 09 Jun 2014 19:19:02 GMT

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

Rick Hillegas commented on DERBY-6533:
--------------------------------------

Here is the output from today's 5 hour run on the 8 core machine. Note that I have been running
with jars built after the checkin of derby-6595-01-aa-dontClearSequenceCache.diff.

No timeouts. No errors.

{noformat}
STATISTICS OF OPERATIONS DONE
-----------------------------



Start time = 2014-06-09 16:04:13.132
End time = 2014-06-09 21:04:13.146
Duration = 300 minutes



SUCCESSFUL: 
	Number of INSERTS = 2163490
	Number of UPDATES = 1066712
	Number of DELETES = 1065886
	Number of SELECTS = 91015

FAILED: 
	Number of failed INSERTS = 0
	Number of failed UPDATES = 1035674
	Number of failed DELETES = 1036857
	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 = 2193783


Last total memory = 6431965184, last free memory = 6295842656 as measured at Mon Jun 09 21:00:57
CEST 2014
{noformat}

> 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: 10.11.0.0
>            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, 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
(v6.2#6252)

Mime
View raw message