[Rev 02] RFR: 6643: Make VM Operations rule consider close consecutive events in score

Jessye Coleman-Shapiro jescolem at openjdk.java.net
Mon Feb 24 17:39:19 UTC 2020


> This patch modifies the VM Operations rule's score calculation so that is considers blocking that could result from the combination of multiple close consecutive operations.  Right now an application's score only takes into account the longest event in its calculation. 
> 
> At the moment I have determined two events to be "close" if they occur within 0.01 s of one another.

The pull request has been updated with 1 additional commit.

-------------

Added commits:
 - d4950e2f: Fix failing tests

Changes:
  - all: https://git.openjdk.java.net/jmc/pull/42/files
  - new: https://git.openjdk.java.net/jmc/pull/42/files/19fb291d..d4950e2f

Webrevs:
 - full: https://webrevs.openjdk.java.net/jmc/42/webrev.02
 - incr: https://webrevs.openjdk.java.net/jmc/42/webrev.01-02

  Stats: 2 lines in 1 file changed: 0 ins; 1 del; 1 mod
  Patch: https://git.openjdk.java.net/jmc/pull/42.diff
  Fetch: git fetch https://git.openjdk.java.net/jmc pull/42/head:pull/42

PR: https://git.openjdk.java.net/jmc/pull/42


More information about the jmc-dev mailing list