6936: Parser should track statistics during parsing

[jpbempel]

Add new IParserStats interface implemented by EventCollection.
That way, IItemCollection is not touched, but you need to cast the
instance to IParserStats.
Support of old (v0.x) JFR format.
During parsing, we collect number of events per type, the size, number
of chunks and version of the file.
We also track for version 1.x/2.x the number of skipped events.
RecordingPrinter tool class is modified to support a summary verbosity mode
and -summary option to print statistics per event type.

---

Progress

• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JMC-6936: Parser should track statistics during parsing

Reviewers

• Marcus Hirt (@thegreystone - Reviewer)

Download

$ git fetch https://git.openjdk.java.net/jmc pull/219/head:pull/219
$ git checkout pull/219

[bridgekeeper]

👋 Welcome back jpbempel! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[mlbridge]

Webrevs

• 03: Full - Incremental (9abc196)
• 02: Full - Incremental (0ea61a1)
• 01: Full - Incremental (9f96658)
• 00: Full (b211354)

[jpbempel]

Made public to be able to use it from here:

jmc/core/org.openjdk.jmc.flightrecorder/src/main/java/org/openjdk/jmc/flightrecorder/internal/parser/v0/EventParserManager.java

Line 100 in 9f96658

String typeId = JdkTypeIDsPreJdk11.translate(id);

[thegreystone]

If we make that class public, we might as well rename it. Since the JDK 8 backport, it really is Oracle type IDs - so perhaps OracleJdkTypeIDsPre11?

[jpbempel]

done

[thegreystone]

Do we need the number of events per type? Isn't that the same as a count aggregate with a type filter?

[jpbempel]

Do we need the number of events per type? Isn't that the same as a count aggregate with a type filter?

Sure it's the same (or should be 😁 ) but at least you have this information close to the other ones to interpret them

[openjdk]

@jpbempel This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

6936: Parser should track statistics during parsing

Reviewed-by: hirt

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@thegreystone) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[jpbempel]

/integrate

[openjdk]

@jpbempel
Your change (at version 9abc196) is now ready to be sponsored by a Committer.

[thegreystone]

/sponsor

[openjdk]

@thegreystone @jpbempel Pushed as commit 0c7ae2a.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.