Project

General

Profile

Feature #1916

improve the runtime statistics gathered by P2J

Added by Constantin Asofiei over 13 years ago. Updated over 10 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Start date:
Due date:
% Done:

0%

billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:

ca_test20091007d.zip (63.9 KB) Constantin Asofiei, 11/09/2012 06:46 AM

History

#1 Updated by Constantin Asofiei over 13 years ago

The attached files contain changes which expand the metrics gathered by BlockManager (to include total execution time) and also adds metric gathering to the Persistence class (related to execution count and time spent during commit, rollback, transactions, and more).

This was originally worked as part of #1198, as a means to identify what slowed down the report.

#2 Updated by Paul E over 10 years ago

This sounds interesting. How do I enable gathering of these statistics?

#3 Updated by Constantin Asofiei over 10 years ago

Paul, I think the stats are enabled by setting a block-execution-statistics attribute in the directory (which represents a file name where to write the data). The stats data will be written after the P2J server is gracefully terminated (i.e. not killed).

The block-execution-statistics node must be defined like this, under i.e. runtime/default/ node:

            <node class="string" name="block-execution-statistics">
              <node-attribute name="value" value="stats-file.txt"/>
            </node>

But there is an issues here: access to BlockManager.stats is not yet synchronized, so running more than one client while the stats are activated will not be safe.

Also available in: Atom PDF