summaryrefslogtreecommitdiff
path: root/site/docs/getting-started/2-experiment.mdx
diff options
context:
space:
mode:
authorDante Niewenhuis <d.niewenhuis@hotmail.com>2024-09-16 11:29:26 +0200
committerGitHub <noreply@github.com>2024-09-16 11:29:26 +0200
commit4a010c6b9e033314a2624a0756dcdc7f17010d9d (patch)
tree70dc26e98cf8421eb5db7f62cf63d4ea2399c505 /site/docs/getting-started/2-experiment.mdx
parent5047e4a25a0814f96852882f02c4017e1d5f81e7 (diff)
All simulation are now run with a single CPU and single MemoryUnit. multi CPUs are combined into one. This is for performance and explainability. (#255)
Diffstat (limited to 'site/docs/getting-started/2-experiment.mdx')
-rw-r--r--site/docs/getting-started/2-experiment.mdx2
1 files changed, 1 insertions, 1 deletions
diff --git a/site/docs/getting-started/2-experiment.mdx b/site/docs/getting-started/2-experiment.mdx
index e25dffc9..14970ea6 100644
--- a/site/docs/getting-started/2-experiment.mdx
+++ b/site/docs/getting-started/2-experiment.mdx
@@ -31,7 +31,7 @@ The baseline for comparison in a portfolio is the **base scenario**. It represen
or, when planning infrastructure from scratch, it consists of very simple base workloads and topologies.
The other scenarios in a portfolio, called the **candidate scenarios**, represent changes to the configuration
that might be of interest to the datacenter designer. Dividing scenarios into these two categories ensures that any
-comparative insights provided by OpenDC are meaningful within the context of the current architecture.
+comparative insights provided by OpenDC are meaningful within the simHyperVisorContext of the current architecture.
To create a new scenario, open a portfolio in the OpenDC web interface and click on ‘+ New Scenario’ in the top right
corner of the scenario table. This opens a modal with the following options (as shown in [Figure 1](#explore)):