Physics underpins computing hardware and the limits of efficiency: how transistors switch, how heat flows, and where new paradigms such as quantum and neuromorphic computing may change what is possible. In this field it grounds claims about hardware performance and energy.
Physics studies matter, energy and their interactions, from fundamental particles to large-scale systems. It provides the governing equations used across hazard modelling, sensing and engineering. In data and compute and energy, physical principles constrain hazard models, sensor design and engineering limits. They help distinguish physically plausible scenarios from implausible ones. The canonical description is on the STEM Commons.
Energy limits of computation
The energy per operation of current hardware is compared with physical limits and with trends, to judge how much further efficiency can improve.
Thermal management physics
Heat transfer in dense racks and chips is modelled to understand cooling limits as power density rises.
Assessing new computing paradigms
Claims for quantum, analogue and neuromorphic computing are compared on the problems where each could outperform classical computing.
03Monitor
Quantum experiment.
The screen a team would use to follow this method: its measures, states and decisions. Names are examples and values are illustrative.
Quantum experiment
Data and compute · Physics of computing · Run R-6942
Calibration runGCRI · Data and Compute
Qubit calibration
Q0
108
130
0.003
In spec
Q1
120
109
0.004
Drifting
Q2
124
132
0.006
Drifting
Q3
142
76
0.008
Drifting
Method card
Method
Physics and quantum science
Device
example testbed
Shots
18,906
Label
MODELLED
Randomised benchmarking
Quantum experiment: the screen's structure, terms and states for Data and compute.Example names and illustrative values; a design, not a record or a live system.
04Data
What the method consumes.
Datasets and records used by physics and quantum science on this platform, with the role each plays and the label its values carry. Sources are listed in the source register.
Data
Role
Label
Device and chip specifications
Energy per operation
DECLARED
Thermal measurements
Heat transfer
OBSERVED
Peer-reviewed benchmarks
Paradigm comparison
REPORTED
05Methods and evidence
How physics of computing is modelled, measured and tested.
The model, its assumptions, its data and its uncertainty, in the form a scientist or engineer would check. Structures follow published methods. The values drawn are illustrative, not findings.
Datasets and provenance
The data classes behind physics of computing and what is recorded about each before it is used.
Data classes and the provenance fields recorded for each; a dataset is listed by name only once its licence admits the use.
FAIR guiding principles · GO FAIR and FORCE11W3C PROV · World Wide Web ConsortiumGuidance on consistent treatment of uncertainties · IPCCCEOS Analysis Ready Data · Committee on Earth Observation Satellites
06Validation
How results are checked.
Theories are tested by reproducible experiments and precise measurement. Numerical codes are verified against analytical solutions and benchmark problems.
Check
How it is done
Peer-reviewed evidence
Performance claims rely on reproducible, peer-reviewed results
Like-for-like comparison
Paradigms are compared on the same problems and metrics
Physical plausibility
Claims are checked against known physical limits
Idealised models may omit friction, heterogeneity or coupling present in real systems. Scale transfer from laboratory to field introduces error.
07Process
How the process runs.
Process explorer · Process
Physics of computing: Post-quantum cryptography migration
8 steps·4 stages
Process
Physics of computing: Post-quantum cryptography migration
NIST published FIPS 203, 204 and 205 on 13 August 2024; the migration steps are common practice, and the IR 8547 timeline is a draft.
01 Discover
01Cryptographic inventoryDatasetOrganisations must find where vulnerable algorithms are used and plan to replace or update them. The inventory lists algorithms and keys.
02Prioritise by data lifetime and exposureStepIR 8547 names the harvest now, decrypt later threat. Systems holding long-lived sensitive data come first.
02 Plan
03Select standardised algorithmsStepFIPS 203, 204 and 205 specify ML-KEM, ML-DSA and SLH-DSA. Falcon and HQC were selected for ongoing standardisation.
04Vendor roadmapsDataset · Data stewardHardware security modules and libraries need vendor support for the selected algorithms. Roadmaps come from each vendor.
03 Deploy
05Hybrid deploymentModelIR 8547 says migration may start with hybrids of quantum-resistant and quantum-vulnerable algorithms, secure if one component is secure.
06TestExerciseInteroperability, performance and fallback are tested before cut-over.
07Cut over and retireDecision · Data stewardIn draft IR 8547, 112-bit public-key algorithms are deprecated after 2030 and quantum-vulnerable ones disallowed after 2035.
04 Sustain
08Crypto agilityStepCrypto agility is the ability to replace and adapt cryptographic algorithms while preserving security and ongoing operations.
Neutral outline of a published external standard or method, from its issuing body. Not a record of operation. Nexus does not perform, certify or approve any step shown. A gate or decision belongs to the party the source names.
What are the limits of physics and quantum science in this field?
Idealised models may omit friction, heterogeneity or coupling present in real systems. Scale transfer from laboratory to field introduces error.
How are results checked?
Theories are tested by reproducible experiments and precise measurement. Numerical codes are verified against analytical solutions and benchmark problems.
Are the values on this page real?
The data names, roles and checks are real descriptions of practice. The canvas shows a design of the method's use, not a run; no result is reported here.
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.
GCRIData and ComputeExponential TechnologyStrategic Systems
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.
Data and Compute
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.
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.
Editors and the expert reviewers named on each article decide what we publish. Funders and partners do not review or approve articles before publication.
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information.
Details
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information. We run no advertising. You can review your choices at any time through Privacy choices at the foot of every page.