Github user srowen commented on the issue:
https://github.com/apache/spark/pull/13618
Yeah this does not guarantee that you won't fill the old generation, though
that's always been a possibility. It does tend to keep all Spark's likely
tenured objects within the old generation. Really, lots of real-world use cases
have always needed a higher non-default setting for `NewRatio`. If you mostly
fill `spark.memory.fraction` with cached data now you'll definitely fill the
old gen.
I think this was an issue in 1.6 in that setting
`spark.storage.memoryFraction` to 0.75 and filling up the cache would also run
over the old gen.
Really I'm just sense-checking the change; it makes sense but I also am
sort of surprised we didn't encounter this before?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
