File: control

package info (click to toggle)
perfmark-java 0.21.0%2Bds-3
  • links: PTS, VCS
  • area: main
  • in suites: bookworm, forky, sid, trixie
  • size: 860 kB
  • sloc: java: 4,963; xml: 13; makefile: 5
file content (57 lines) | stat: -rw-r--r-- 2,450 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
Source: perfmark-java
Section: java
Priority: optional
Maintainer: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
Uploaders: Olek Wojnar <olek@debian.org>
Build-Depends: debhelper-compat (= 13),
               default-jdk,
               gradle-apt-plugin,
               gradle-debian-helper,
               libasm-java,
               libbyte-buddy-java,
               liberror-prone-java,
               libgradle-plugins-java,
               libjsr305-java,
               maven-repo-helper,
Standards-Version: 4.6.2
Rules-Requires-Root: no
Vcs-Git: https://salsa.debian.org/java-team/perfmark-java.git
Vcs-Browser: https://salsa.debian.org/java-team/perfmark-java
Homepage: https://github.com/perfmark/perfmark

Package: libperfmark-java
Architecture: all
Multi-Arch: foreign
Depends: ${misc:Depends}
Description: High Performance Tracing Library for Java
 Low-overhead, manually-instrumented, tracing library for Java. Users can add
 the tracing function calls to their code to see how long each part takes.
 .
 Features
 .
  * Very Low Overhead: When enabled, tracing a function call adds about 70ns.
    Tracing is done in a lock-free, wait-free, thread local buffer, which
    avoids interfering with your latency-sensitive code.
 .
  * Dynamically Enabled: PerfMark can be enabled or disabled at runtime. When
    disabled, PerfMark has zero overhead, taking advantage of the JIT compiler
    to remove the tracing.
 .
  * Inter-thread Communication: Existing profilers have difficulty expressing
    which thread wakes up and executes work on another thread. PerfMark allows
    users to express this relationship explicitly, making for a clear picture
    of how code flows.
 .
  * Small Library Size: The PerfMark tracing API is only 5 KB in size, and has
    minimal dependencies making it easy to include in other projects. If no
    backend for recording the trace is present, the library safely disables
    itself.
 .
  * Multiple Java Versions: The PerfMark API supports Java 6, making it easy to
    include on older or constrained environments. Additionally, PerfMark
    includes optimized backends for Java 6, Java 7, and Java 9. Each of these
    backends is automatically loaded at runtime (if possible) and uses advanced
    JVM features for maximum speed.
 .
  * Chrome Trace Viewer Integration: PerfMark can export to the Chrome Trace
    Event Format, making it easy to view in your Web Browser.