Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 10 Jun 2014 18:55:01 +0000 (UTC)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <JIRA.12705676.1396278294963.103573.1402426501885@arcas>
In-Reply-To: <JIRA.12705676.1396278294963@arcas>
References: <JIRA.12705676.1396278294963@arcas>
Subject: [jira] [Commented] (DERBY-6533) Add a quiet mode to NsTest
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Here's the output from today's 6 hour run on the 8 core machine. No timeouts. No errors.

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


Start time = 2014-06-10 13:50:40.878
End time = 2014-06-10 19:50:40.889
Duration = 360 minutes


SUCCESSFUL: 
	Number of INSERTS = 2524739
	Number of UPDATES = 1242978
	Number of DELETES = 1243728
	Number of SELECTS = 102539

FAILED: 
	Number of failed INSERTS = 0
	Number of failed UPDATES = 1205841
	Number of failed DELETES = 1207385
	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 = 2555362


Last total memory = 6413090816, last free memory = 4674349760 as measured at Tue Jun 10 19:47:24 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)