-
Enhancement
-
Resolution: Fixed
-
P3
-
6
-
b01
-
generic, x86
-
generic, linux
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2204629 | 7 | Paul Hohensee | P3 | Closed | Fixed | b128 |
M&M: approximate memory allocation rate per thread (already prioritized as low GD)
It should be posssible to track the approximate mmemory
allocation rate per thread.
The maain purpose here is to detect a thread that has gone wild.
###@###.### 10/4/04 13:06 GMT
It should be posssible to track the approximate mmemory
allocation rate per thread.
The maain purpose here is to detect a thread that has gone wild.
###@###.### 10/4/04 13:06 GMT
- backported by
-
JDK-2204629 M&M: approximate memory allocation rate/amount per thread
-
- Closed
-
- duplicates
-
JDK-6422028 Per-thread allocation tally
-
- Closed
-
- relates to
-
JDK-7013682 two test checking cpuTime filed java/lang/management/ThreadMXBean
-
- Closed
-
-
JDK-7015368 getThreadCpuTime() and getThreadUserTime() methods act incorrectly
-
- Closed
-
-
JDK-6937077 Dump allocations per thread based on the TLABS statistics
-
- Closed
-
-
JDK-7003271 Hotspot should track cumulative Java heap bytes allocated on a per-thread basis
-
- Closed
-
(1 relates to)