Github user nishkamravi2 commented on the pull request:
https://github.com/apache/spark/pull/1391#issuecomment-49483642
6% was experimentally obtained (with the goal of keeping the bound as tight
as possible without the containers crashing). Three workloads were experimented
with: PageRank, WordCount and KMeans over moderate to large input datasets and
configured such that the containers are optimally utilized (neither
under-utilized nor over-subscribed). Based on my observations, less than 5% is
a no-no. If someone would like to tune this parameter more and make a case for
a higher value (keeping in mind that this is a default value that will not
cover all workloads), that would be helpful.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
