High-throughput computing: Difference between revisions
No edit summary |
|||
| Line 7: | Line 7: | ||
==High-throughput computing vs. high-performance computing vs. many-task computing== |
==High-throughput computing vs. high-performance computing vs. many-task computing== |
||
There are many differences between '''high-throughput computing''', [[high-performance computing]] (HPC), and [[many-task computing]] (MTC). HPC tasks are characterized as needing large |
There are many differences between '''high-throughput computing''', [[high-performance computing]] (HPC), and [[many-task computing]] (MTC). HPC tasks are characterized as needing large amounts of computing power for short periods of time, whereas HTC tasks also require large amounts of computing, but for much longer times (months and years, rather than hours and days) <ref>{{cite web|url=http://www.hpcwire.com/hpc-bin/artread.pl?direction=Current&articlenumber=11444|first=Alan|last=Beck|date = [[1997-06-27]]|publisher=HPCWire|title=High Throughput Computing: An Interview with Miron Livny}}</ref>. HPC environments are often measured in terms of [[FLOPS]]. The HTC community, however, is not concerned about operations per second, but rather operations per month or per year. Therefore, the HTC field is more interested in how many jobs can be completed over a long period of time instead of how fast an individual job can complete. |
||
As a general rule, HPC systems are tightly coupled [[parallel computing|parallel]] jobs, and as such they must execute within a particular site with low-latency interconnects. Conversely, HTC systems are independent, sequential jobs that can be individually scheduled on many different computing resources across multiple administrative boundaries. HTC systems achieve this using various [[grid computing]] technologies and techniques. |
As a general rule, HPC systems are tightly coupled [[parallel computing|parallel]] jobs, and as such they must execute within a particular site with low-latency interconnects. Conversely, HTC systems are independent, sequential jobs that can be individually scheduled on many different computing resources across multiple administrative boundaries. HTC systems achieve this using various [[grid computing]] technologies and techniques. |
||
Revision as of 12:48, 11 December 2009
High-throughput computing (HTC) is a computer science term to describe the use of many computing resources over long periods of time to accomplish a computational task.
Challenges
The HTC community is also concerned with robustness and reliability of jobs over a long-time scale. That is, being able to create a reliable system from unreliable components. This research is similar to transaction processing, but at a much larger and distributed scale.
Some HTC systems, such as Condor and PBS, can run tasks on opportunistic resources. It is a difficult problem, however, to operate in this environment. On one hand the system needs to provide a reliable operating environment for the user's jobs, but at the same time the system must not compromise the integrity of the execute node and allow the owner to always have full control of their resources.
High-throughput computing vs. high-performance computing vs. many-task computing
There are many differences between high-throughput computing, high-performance computing (HPC), and many-task computing (MTC). HPC tasks are characterized as needing large amounts of computing power for short periods of time, whereas HTC tasks also require large amounts of computing, but for much longer times (months and years, rather than hours and days) [1]. HPC environments are often measured in terms of FLOPS. The HTC community, however, is not concerned about operations per second, but rather operations per month or per year. Therefore, the HTC field is more interested in how many jobs can be completed over a long period of time instead of how fast an individual job can complete.
As a general rule, HPC systems are tightly coupled parallel jobs, and as such they must execute within a particular site with low-latency interconnects. Conversely, HTC systems are independent, sequential jobs that can be individually scheduled on many different computing resources across multiple administrative boundaries. HTC systems achieve this using various grid computing technologies and techniques.
MTC aims to bridge the gap between HTC and HPC. MTC is reminiscent of HTC, but it differs in the emphasis of using many computing resources over short periods of time to accomplish many computational tasks (i.e. including both dependent and independent tasks), where the primary metrics are measured in seconds (e.g. FLOPS, tasks/s, MB/s I/O rates), as opposed to operations (e.g. jobs) per month. MTC denotes high-performance computations comprising multiple distinct activities, coupled via file system operations.
See also
HTC is not only for sequential jobs but also for parallel jobs.
References
- ^ Beck, Alan (1997-06-27). "High Throughput Computing: An Interview with Miron Livny". HPCWire.
{{cite web}}: Check date values in:|date=(help)