• 首页
• HFSS教程
• ADS教程
• CST教程
• 射频工程师培训
• 微波仪器操作培训
• 天线设计培训
• 射频专业基础课

Ansoft Designer / Ansys Designer 在线帮助文档：

Windows HPC Integration >
   HPC Integration Guidelines >
       Job Unit Type           

Job Unit Type

The Job Unit Type is the smallest unit of processing resources used to schedule a job and is one of the most important job properties. There are three options for the Job Unit Type: Core, Socket, and Node.

• Core: Jobs are scheduled in units of cores, also referred to as CPU cores, logical processors, or CPUs. This is the finest unit of granularity available. This selection allows the scheduler to start multiple tasks on a processor if the total number of cores needed by the tasks is less than or equal to the number of cores on the processor. This selection also allows the scheduler to distribute more of the computational load to processors with more available cores.

• Socket: A socket, also referred to as a NUMA node, is a collection of cores sharing a direct connection to memory. A socket contains at least one core, but may contain several cores. The socket concept may not necessarily correspond to a physical socket. Scheduling at the socket level may be useful in cases where each task requires extensive use of the memory bus, as scheduling multiple tasks on the same socket would result in excessive bus contention.

• Node: Jobs are scheduled in units of nodes, hosts, or machines. This is the coarsest level of granularity available. When this option is selected, only one task will run on any give node at a time. This is useful in cases where it is not desirable to run multiple tasks on a single host. For example, if each task is multi-threaded, running multiple tasks on the same node may not be required in order to fully utilize the computing resources on the node. This may also be preferred if a task is memory intensive, as multiple tasks will be competing for limited resources.

How to Select the Job Unit Type

When the unit type is selected for a job, it also applies to all of the tasks of the job. It is important to select the job unit type before selecting job units or job tasks because the unit type affects many other choices. For example, if the unit type for the job is Node, then you cannot schedule tasks in units of Core.

• If the job tasks are CPU bound, it is usually best to select a unit type of Core. This allows the tasks to be distributed to as many cores as possible, making maximum use of the computational resources available. This choice may also allow cores that are not currently assigned to a job to be used by other jobs.

• If the job tasks are memory bound, a unit type of Socket may be a better selection. Running multiple tasks on the same socket may decrease performance due to memory bus contention. Some experimentation may be needed to determine whether a Socket or Core unit type is more efficient.

• The Node unit type selection may be best if the tasks in question are multi-threaded and will effectively use the computing resources available. In this case, there may be no benefit to scheduling multiple tasks on a node. The Node unit type may also be the best selection if a system-wide resource is the source of the bottleneck, such as:

— Each task requires all the memory available on the node, and running multiple tasks results in excessive paging or swapping

— Each task is limited by bandwidth of the disk connection

— Each task is limited by network bandwidth

                HFSS视频教程                                      ADS视频教程                               CST视频教程                           Ansoft Designer 中文教程

      Copyright © 2006 - 2013   微波EDA网, All Rights Reserved    业务联系：mweda@163.com