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 Thu, 22 May 2014 19:07:07 GMT

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

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

I have updated the version of Derby used on the 8 core machine again. This version incorporates
changes to the mainline up through the checkin of derby-6542-03-aa-lockTimeoutForIdentityContention.diff.
I am including the results of today's 6 hour run. Summary: no errors, no timeouts.

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



Start time = 2014-05-22 14:12:40.609
End time = 2014-05-22 20:12:40.619
Duration = 360 minutes



SUCCESSFUL: 
	Number of INSERTS = 2450284
	Number of UPDATES = 1207723
	Number of DELETES = 1206995
	Number of SELECTS = 100299

FAILED: 
	Number of failed INSERTS = 0
	Number of failed UPDATES = 1170966
	Number of failed DELETES = 1172099
	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 = 2479872


Last total memory = 6371147776, last free memory = 4946252504 as measured at Thu May 22 20:09: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
>
>
> 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