1 / 7

Computational Resource Consumption with SpoRT

This document details the assessment of computational resource usage within the SPoRT program, focusing on tasks deemed computationally "expensive," defined as multiprocessor tasks running for over an hour. The evaluation includes examining the number of processors, task durations, and experiment counts to quantify necessary computational hours for each experimental step. Individual studies such as the AIRS profile and NSSL forecasts are analyzed for CPU resource allocation, providing critical insights into resource efficiency and planning.

mayten
Télécharger la présentation

Computational Resource Consumption with SpoRT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Computational Resource Consumption with SpoRT Assessment of Computational Resource usage within the SPoRT program October 2007

  2. Current Activities • Activities in this assessment are only those deemed to be computationally “expensive” • The definition of expensive is generally tasks that are multiprocessor tasks and run for a notable amount of time (generally greater than an hour) 1 Since ADAS is single processor, only fcst is included in this discussion

  3. Quantifying Current Activities • Basic measures needed to determine a quantified comparison of computational resource consumption • the number of processors • the time per individual task • the number of experiments • The product of these measures gives a measure of the computational hours necessary for each “step” within the experimental design • Processor efficiency is not considered

  4. Quantifying Current Activities

  5. Quantifying Current Activities • The previous chart shows the amount of resources per experimental step • However, each study has more steps per case day • For example, the AIRS profile study runs once a case day • The NSSL forecasts are initialized once a day • The AIRS Radiance study performs 8 assimilation cycles and 4 forecasts a day • Thus, computational hours per case day are considered by taking the product of the steps per day and the computational hours per step

  6. Quantifying Current Activities 1 The Radiance Assimilation study is the total of the DA cycle and the spawned forecasts

  7. Disk Space Requirement Estimation 1 DA+FCST 2 “Total”

More Related