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/06/05 21:17:01 UTC
[jira] [Comment Edited] (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=14019118#comment-14019118 ]
Rick Hillegas edited comment on DERBY-6533 at 6/5/14 7:15 PM:
--------------------------------------------------------------
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-05 13:46:33.618
End time = 2014-06-05 19:46:33.633
Duration = 360 minutes
SUCCESSFUL:
Number of INSERTS = 2576702
Number of UPDATES = 1270999
Number of DELETES = 1267990
Number of SELECTS = 103788
FAILED:
Number of failed INSERTS = 0
Number of failed UPDATES = 1230041
Number of failed DELETES = 1231559
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 = 2612586
Last total memory = 6429868032, last free memory = 5868794056 as measured at Thu Jun 05 19:43:17 CEST 2014
{noformat}
was (Author: rhillegas):
Here's the output from today's 6 hour run on the core machine. No timeouts. No errors.
{noformat}
STATISTICS OF OPERATIONS DONE
-----------------------------
Start time = 2014-06-05 13:46:33.618
End time = 2014-06-05 19:46:33.633
Duration = 360 minutes
SUCCESSFUL:
Number of INSERTS = 2576702
Number of UPDATES = 1270999
Number of DELETES = 1267990
Number of SELECTS = 103788
FAILED:
Number of failed INSERTS = 0
Number of failed UPDATES = 1230041
Number of failed DELETES = 1231559
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 = 2612586
Last total memory = 6429868032, last free memory = 5868794056 as measured at Thu Jun 05 19:43:17 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)