Skip to content

GCRI · Technology

High-performance, cloud and edge computing

High-performance, cloud and edge computing provide the processing and storage capacity for simulation, analytics and digital services. They are both an enabler of risk analysis and a critical dependency for society. Data and Compute stewards this page for the Nexus Consortium.

Make an enquiry Back to Technology
01Contents

High-performance, cloud and edge computing in six parts.

In this dossier6 parts
  1. 01The methodWhat high-performance, cloud and edge computing covers
  2. 02Reference practiceComputing practice is measured by performance, efficiency and reproducibility
  3. 03In systemic risk workCompute sets the resolution of what can be known
  4. 04Applied inPlatforms that apply this method
  5. 05StewardshipWho maintains this page
  6. 06SourcesWhere this page’s references lead
02The method

What high-performance, cloud and edge computing covers.

  1. 01

    Core methods

    parallel and distributed computing; workload scheduling; virtualisation and containerisation; capacity planning; fault-tolerant system design; performance benchmarking.

  2. 02

    Data and instruments

    system performance logs; job scheduler records; energy and cooling telemetry; benchmark results; service availability records.

  3. 03

    Validation

    Systems are tested through benchmarks, load testing and failover exercises. Numerical reproducibility is checked across hardware and software configurations.

  4. 04

    Limits

    Concentration in few providers or regions creates shared points of failure. Energy, water and supply chain constraints limit capacity growth.

  5. 05

    Use in risk decisions

    Computing capacity determines how fast and at what resolution risks can be modelled. Its concentration is itself a systemic dependency for finance, health and government services.

03Reference practice

Computing practice is measured by performance, efficiency and reproducibility.

ReferenceWhat it sets
TOP500 and Green500Published lists of supercomputer performance and energy efficiency
ISO/IEC 30134 seriesData-centre efficiency indicators
MLCommons benchmarksMachine-learning performance benchmarks
04Process

How the process runs.

Process

High-performance, cloud and edge computing: Build, sign and accept

An admitted mission becomes a cycle project; the build is pinned, verified and signed, and the Global Risks Forum (GRF) records acceptance for exercise, not permission to deploy.

  1. 01 Request and sources

    1. 01Admitted mission becomes a cycle projectRecord · Universe to FoundryAn admitted mission becomes a cycle project with a decision case.
    2. 02Qualify data sources and resourcesStep · the Global Centre for Risk and Innovation (GCRI)GCRI qualifies data sources and resource offers and builds the scenario models. An offer is not an allocation.

  2. 02 Build and verify

    1. 03Source snapshotRecord · NXS-FAC (blueprints, builds and signing)The snapshot pins the commit, dependencies and generator versions.
    2. 04Build contractRecord · NXS-FAC (blueprints, builds and signing)The build contract declares the artefact kind, environment and reproducibility envelope.
    3. 05Integrate and buildModel · GCRIGCRI integrates software and data, signs builds, and tests security and interoperability.
    4. 06Verification suiteGate · NXS-FAC (blueprints, builds and signing)Required and advisory checks stay separate. Reproducibility needs pinned inputs, declared nondeterminism and independent rebuilds.

  3. 03 Sign and admit

    1. 07Sign the exact artefactStep · NXS-FAC (blueprints, builds and signing)NXS-FAC builds, attests and requests a signature via a scoped signer identity. It holds no key material.
    2. 08Package admissionStep · NXS-NXQ (software, models and capability lifecycle)NXS-NXQ receives the signed package and keeps admission evidence that binds the task, data class, evaluation suite and expiration.

  4. 04 Accept

    1. 09Core Build ReportRecord · GCRIThe Core Build Report is the go or no-go record. Universe assembles the Core and holds the decision for the exercise.
    2. 10G3 · Build accepted for exerciseGate · The Global Risks ForumGRF records whether the build is accepted for exercise. A signed build or release candidate is not permission to deploy to production.

The programme year · NXS-FAC · UniverseDesigned programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation. The record order follows the Builds and Releases room lists of NXS-FAC.

05In systemic risk work

Compute sets the resolution of what can be known.

Ensemble size, model resolution and the number of scenarios explored are limited by compute. For systemic risk, compute is also a dependency: public services and science rely on a small number of providers. Reproducibility requires recording the software environment and hardware where results depend on them.

  • Record software versions and random seeds.
  • Note when results depend on hardware precision.
  • Assess continuity of access to compute for critical analysis.
  • Applications on Data and Compute and Foundry.
06Applied in

Platforms that apply this method.

07Stewardship

Who maintains this page.

Data and Compute stewards high-performance, cloud and edge computing: it keeps this description current and reviews how the method is applied across the platforms.

08Sources

Where this page’s references lead.

The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.

09Questions

Questions and answers.

Why does one institution host every method page?
GCRI hosts the STEM Commons so that each method has one canonical description. Platforms link to it rather than repeat it, which keeps definitions consistent.
How do I suggest a correction to a method page?
Write to the integrity concern form with the passage and the reason.
ReportsContribute

Contribute evidence from this page.

Reports is the Consortium’s quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.

GCRI

Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.

The Global Centre for Risk and Innovation

Bring a method, a dataset or a question.

Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.

Propose a method See all contact routes
Legal

Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.

Privacy choices