You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Aaron Davidson (JIRA)" <ji...@apache.org> on 2014/11/12 19:14:33 UTC

[jira] [Created] (SPARK-4370) Limit cores used by Netty transfer service based on executor size

Aaron Davidson created SPARK-4370:
-------------------------------------

             Summary: Limit cores used by Netty transfer service based on executor size
                 Key: SPARK-4370
                 URL: https://issues.apache.org/jira/browse/SPARK-4370
             Project: Spark
          Issue Type: Bug
          Components: Spark Core
    Affects Versions: 1.2.0
            Reporter: Aaron Davidson
            Assignee: Aaron Davidson
            Priority: Critical


Right now, the NettyBlockTransferService uses the total number of cores on the system as the number of threads and buffer arenas to create. The latter is more troubling -- this can lead to significant allocation of extra heap and direct memory in situations where executors are relatively small compared to the whole machine. For instance, on a machine with 32 cores, we will allocate (32 cores * 16MB per arena = 512MB) * 2 for client and server = 1GB direct and heap memory. This can be a huge overhead if you're only using, say, 8 of those cores.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org