Performance data/impact for users to determine what jlink optimization should be selected

Feedback from Aurelio:

jlink offers these built-in optimization at the moment and maybe more in the future:
  -G, --strip-debug Strip debug information
  -c, --compress=2 Enable compression of resources (level 2)

For developers to determine what options should be selected, it'd be useful to provide performance data such as impact on runtime and footprint that would help guide the jlink users.

Probably such information would publish in a user guide or some kind of documentation.