[ 
https://issues.apache.org/jira/browse/BEAM-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17137229#comment-17137229
 ] 

Beam JIRA Bot commented on BEAM-7684:
-------------------------------------

This issue was marked "stale-P2" and has not received a public comment in 14 
days. It is now automatically moved to P3. If you are still affected by it, you 
can comment and move it back to P2.

> WindmillStateCache grossly misunderestimates object size in its weighting 
> function
> ----------------------------------------------------------------------------------
>
>                 Key: BEAM-7684
>                 URL: https://issues.apache.org/jira/browse/BEAM-7684
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow
>            Reporter: Steve Niemitz
>            Priority: P3
>
> As a little experiment, we set the WindmillStateCache size to 2 GB.  After we 
> let a job run for a few hours, the workers all died from OOMs.  Digging into 
> the memory usage, over 10 GB of heap was used by the WindmillStateCache.  The 
> total weight the cache had calculated however was only ~800 MB.
> It looks like the StateCacheEntry calculation is way off.  The weight of an 
> entry was calculated as only ~200, while the actual heap usage of it (as 
> reported by YourKit at least) was around 2,400 bytes.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to