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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2014/05/01 21:07:17 UTC

[jira] [Commented] (DERBY-6533) Add a quiet mode to NsTest

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

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

Here is the output from today's 6 hour run of NsTest on the 8 core machine using the derby-6542-02-ab-useNewSequenceGenerator.diff patch. No errors. No timeouts.

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



Start time = 2014-05-01 14:56:07.471
End time = 2014-05-01 20:56:07.483
Duration = 360 minutes



SUCCESSFUL: 
	Number of INSERTS = 2572569
	Number of UPDATES = 1266035
	Number of DELETES = 1267002
	Number of SELECTS = 104725

FAILED: 
	Number of failed INSERTS = 0
	Number of failed UPDATES = 1233442
	Number of failed DELETES = 1231390
	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 = 2608146


Last total memory = 6314524672, last free memory = 5839454304 as measured at Thu May 01 20:52:51 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
>
>
> 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)