| 1 |
Source: perfmark-java |
| 2 |
Section: java |
| 3 |
Priority: optional |
| 4 |
Maintainer: Debian Java Maintainers <[email protected]> |
| 5 |
Uploaders: Olek Wojnar <[email protected]> |
| 6 |
Build-Depends: debhelper-compat (= 13), |
| 7 |
default-jdk, |
| 8 |
gradle-apt-plugin, |
| 9 |
gradle-debian-helper, |
| 10 |
libasm-java, |
| 11 |
libbyte-buddy-java, |
| 12 |
liberror-prone-java, |
| 13 |
libgradle-plugins-java, |
| 14 |
libjsr305-java, |
| 15 |
maven-repo-helper, |
| 16 |
Standards-Version: 4.6.2 |
| 17 |
Rules-Requires-Root: no |
| 18 |
Vcs-Git: https://salsa.debian.org/java-team/perfmark-java.git |
| 19 |
Vcs-Browser: https://salsa.debian.org/java-team/perfmark-java |
| 20 |
Homepage: https://github.com/perfmark/perfmark |
| 21 |
|
| 22 |
Package: libperfmark-java |
| 23 |
Architecture: all |
| 24 |
Multi-Arch: foreign |
| 25 |
Depends: ${misc:Depends} |
| 26 |
Description: High Performance Tracing Library for Java |
| 27 |
Low-overhead, manually-instrumented, tracing library for Java. Users can add |
| 28 |
the tracing function calls to their code to see how long each part takes. |
| 29 |
. |
| 30 |
Features |
| 31 |
. |
| 32 |
* Very Low Overhead: When enabled, tracing a function call adds about 70ns. |
| 33 |
Tracing is done in a lock-free, wait-free, thread local buffer, which |
| 34 |
avoids interfering with your latency-sensitive code. |
| 35 |
. |
| 36 |
* Dynamically Enabled: PerfMark can be enabled or disabled at runtime. When |
| 37 |
disabled, PerfMark has zero overhead, taking advantage of the JIT compiler |
| 38 |
to remove the tracing. |
| 39 |
. |
| 40 |
* Inter-thread Communication: Existing profilers have difficulty expressing |
| 41 |
which thread wakes up and executes work on another thread. PerfMark allows |
| 42 |
users to express this relationship explicitly, making for a clear picture |
| 43 |
of how code flows. |
| 44 |
. |
| 45 |
* Small Library Size: The PerfMark tracing API is only 5 KB in size, and has |
| 46 |
minimal dependencies making it easy to include in other projects. If no |
| 47 |
backend for recording the trace is present, the library safely disables |
| 48 |
itself. |
| 49 |
. |
| 50 |
* Multiple Java Versions: The PerfMark API supports Java 6, making it easy to |
| 51 |
include on older or constrained environments. Additionally, PerfMark |
| 52 |
includes optimized backends for Java 6, Java 7, and Java 9. Each of these |
| 53 |
backends is automatically loaded at runtime (if possible) and uses advanced |
| 54 |
JVM features for maximum speed. |
| 55 |
. |
| 56 |
* Chrome Trace Viewer Integration: PerfMark can export to the Chrome Trace |
| 57 |
Event Format, making it easy to view in your Web Browser. |