12.07.2015 Views

GSC Sentinel-2 PDGS STBD - emits - ESA

GSC Sentinel-2 PDGS STBD - emits - ESA

GSC Sentinel-2 PDGS STBD - emits - ESA

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>GSC</strong> <strong>Sentinel</strong>-2 <strong>PDGS</strong> <strong>STBD</strong>Issue 1 Revision 2 (draft) - 25.07.2010GMES-GSEG-EOPG-TN-09-0031page 13 of 60IBM BladeCenter HS21, CPU: Intel Xeon E5430, 2.66 GHz, RAM: 16GB DDR2 667 MHz,Cache: 6144 KB, Storage: IBM Storage and I/O blade (SIO) with 3 SAS disks in RAID-5configuration.In particular, the wording “CPU unit” used in the estimations systematically refers to oneCPU core of the above benchmarking hardware.3.2 Reference BenchmarksThis section collects the results of the reference benchmarks that have been executed atCNES premises to define the GPP processing performances.These benchmarks have been performed considering the GPP layout based on componentsindicated as IAS (shortly recalled in 3.2.1) therefore are not at processing step level.The analysis has been carried out using the hardware description of 3.1.4.The values presented in the next paragraphs correspond to elementary computing times (orcomplexity equivalent) and don’t take into account any possible parallelisation of processing;indeed they correspond to sequential processing (only one core has been activated).They correspond to a Level-0 and Level-1 processing relative to one <strong>Sentinel</strong>-2 averageorbit of 6640km along-track.The benchmarks have been performed on data representative of the <strong>Sentinel</strong>2configuration and extrapolated for the average datastrip.A security margin of 15% has been considered in the unitary processing times to takeinto account the contribution of activities that can be assumed as minor in terms oftime consumption (e.g. the interaction between the supervision subsystem and theprocessing subsystems, data formatting, etc).The benchmark figures measure the processing time (wall clock time) including disksaccess (I/O) in a purely sequential process with access to dedicated resources (oneCPU core and local hard-disk as defined in section 3.1.4). Other transfers of data (e.g.between several workstations) or resource usage bottlenecks potentially introducedby the parallel processing on a shared hardware (e.g. disk I/O on a shared StorageArea Network) are not taken into account.The list of the benchmark results is provided in 3.2.2.3.2.1 THE PROCESSING CHAIN FOR THE BENCHMARKSThe benchmarked processing times reported in this paragraph are based on the GroundPrototype Processor documentation defined in [RD-03].The Figure below shows the processing steps of the Level-0 product and its consolidation.<strong>ESA</strong> UNCLASSIFIED – For Official Use© <strong>ESA</strong>The copyright of this document is the property of <strong>ESA</strong>. It is supplied in confidence and shall not be reproduced, copied orcommunicated to any third party without written permission from <strong>ESA</strong>.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!