You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/04/06 12:40:00 UTC

[jira] [Work logged] (BEAM-14144) Record JFR profiles when GC thrashing is detected

     [ https://issues.apache.org/jira/browse/BEAM-14144?focusedWorklogId=753346&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-753346 ]

ASF GitHub Bot logged work on BEAM-14144:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 06/Apr/22 12:39
            Start Date: 06/Apr/22 12:39
    Worklog Time Spent: 10m 
      Work Description: steveniemitz commented on PR #17151:
URL: https://github.com/apache/beam/pull/17151#issuecomment-1090220360

   ping @lukecwik , thanks!




Issue Time Tracking
-------------------

    Worklog Id:     (was: 753346)
    Time Spent: 2h 40m  (was: 2.5h)

> Record JFR profiles when GC thrashing is detected
> -------------------------------------------------
>
>                 Key: BEAM-14144
>                 URL: https://issues.apache.org/jira/browse/BEAM-14144
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-dataflow
>            Reporter: Steve Niemitz
>            Assignee: Steve Niemitz
>            Priority: P2
>          Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> It'd be useful for debugging GC issues in jobs to have allocation profiles when it was occurring.   In java 9+, JFR is included in the JDK, we could use that to record profiles when GC thrashing is detected.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)