[
https://issues.apache.org/jira/browse/DERBY-6533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13993867#comment-13993867
]
Rick Hillegas edited comment on DERBY-6533 at 5/9/14 7:50 PM:
--------------------------------------------------------------
Here's the output from today's 6 hour run on the 8 core machine, same patch. No
errors. No timeouts.
{noformat}
STATISTICS OF OPERATIONS DONE
-----------------------------
Start time = 2014-05-09 14:07:28.219
End time = 2014-05-09 20:07:28.226
Duration = 360 minutes
SUCCESSFUL:
Number of INSERTS = 2539381
Number of UPDATES = 1251881
Number of DELETES = 1251431
Number of SELECTS = 102455
FAILED:
Number of failed INSERTS = 0
Number of failed UPDATES = 1212376
Number of failed DELETES = 1216299
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 = 2575344
Last total memory = 6335496192, last free memory = 4574617096 as measured at
Fri May 09 20:04:12 CEST 2014
{noformat}
was (Author: rhillegas):
Here's the output from today's 6 hour run on the 8 core machine, same patch. No
errors. No timeouts.
{noformat]
STATISTICS OF OPERATIONS DONE
-----------------------------
Start time = 2014-05-09 14:07:28.219
End time = 2014-05-09 20:07:28.226
Duration = 360 minutes
SUCCESSFUL:
Number of INSERTS = 2539381
Number of UPDATES = 1251881
Number of DELETES = 1251431
Number of SELECTS = 102455
FAILED:
Number of failed INSERTS = 0
Number of failed UPDATES = 1212376
Number of failed DELETES = 1216299
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 = 2575344
Last total memory = 6335496192, last free memory = 4574617096 as measured at
Fri May 09 20:04:12 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)
