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)

3 files changed, 6 insertions, 6 deletions

diff --git a/site/docs/getting-started/0-installation.md b/site/docs/getting-started/0-installation.md
index e0e944cc..e9f539a8 100644
--- a/site/docs/getting-started/0-installation.md
+++ b/site/docs/getting-started/0-installation.md
@@ -40,7 +40,7 @@ __  ____  __  _____   ___  __ ____  ______
 2022-09-12 10:30:22,282 INFO  [org.ope.web.run.run.OpenDCRunnerRecorder] (main) Starting OpenDC Runner in background (polling every PT30S)
 2022-09-12 10:30:22,347 INFO  [io.quarkus] (main) opendc-web-server 2.1-rc1 on JVM (powered by Quarkus 2.11.1.Final) started in 1.366s. Listening on: http://0.0.0.0:8080
 2022-09-12 10:30:22,348 INFO  [io.quarkus] (main) Profile prod activated.
-2022-09-12 10:30:22,348 INFO  [io.quarkus] (main) Installed features: [agroal, cdi, flyway, hibernate-orm, hibernate-validator, jdbc-h2, jdbc-postgresql, kotlin, narayana-jta, opendc-runner, opendc-ui, resteasy, resteasy-jackson, security, smallrye-context-propagation, smallrye-openapi, swagger-ui, vertx]
+2022-09-12 10:30:22,348 INFO  [io.quarkus] (main) Installed features: [agroal, cdi, flyway, hibernate-orm, hibernate-validator, jdbc-h2, jdbc-postgresql, kotlin, narayana-jta, opendc-runner, opendc-ui, resteasy, resteasy-jackson, security, smallrye-simHyperVisorContext-propagation, smallrye-openapi, swagger-ui, vertx]
 ```
 This will launch the built-in single-user OpenDC server on port 8080. Visit
 [http://localhost:8080](http://localhost:8080) to access the bundled web UI.
diff --git a/site/docs/getting-started/1-design.mdx b/site/docs/getting-started/1-design.mdx
index 144fbf98..e8ab2c58 100644
--- a/site/docs/getting-started/1-design.mdx
+++ b/site/docs/getting-started/1-design.mdx
@@ -83,7 +83,7 @@ build rooms. Let’s take a moment to familiarize ourselves with the interface.
 
 If you dismiss the sidebar on your left, you have controls for zooming in and out. Next to the zooming buttons, you also
 have a ‘Screenshot’ button, in case you want to record the state of the canvas and export it to an image file. On the
-right side of the screen, you have the context menu. This menu changes depending on your zoom level.
+right side of the screen, you have the simHyperVisorContext menu. This menu changes depending on your zoom level.
 
 As there are currently no rooms, we are in ‘Building’ mode, and our only option is to ‘Construct a new room’. Click on
 that button to build a first datacenter room - once you’ve clicked on it, every tile of the canvas that you click on
@@ -106,7 +106,7 @@ Create at least a single room, with help of the above instructions.
 
 Once you’ve placed the tiles, you can give the room a name, if you want to. To do this, click on the room you want to
 edit. You’ll notice the application going into ‘Room’ mode, allowing you to manipulate the topology of the datacenter at
-a more fine-grained level. In the context menu, change the room name, and click on the ‘Save’ button. You can exit
+a more fine-grained level. In the simHyperVisorContext menu, change the room name, and click on the ‘Save’ button. You can exit
 ‘Room’ mode by clicking on any of the darkened areas outside of the selected room. This will bring you back to
 ‘Building’ mode.
 
@@ -131,7 +131,7 @@ Add a couple of servers to the rack.
 :::
 
 To add actual servers to the empty racks, we’ll need to go one level deeper in the topological hierarchy of the
-datacenter. Clicking on a rack lets you do just that. Once you’ve clicked on it, you’ll notice the context menu now
+datacenter. Clicking on a rack lets you do just that. Once you’ve clicked on it, you’ll notice the simHyperVisorContext menu now
 displaying slots. In each slot fits exactly one server unit. To add such a server unit, click on the ‘Add machine’
 button of that slot.
 Just like in ‘Room’ mode, you can exit ‘Rack’ mode by clicking on any of the darkened tiles around the currently
@@ -148,7 +148,7 @@ Populate the machines with CPU and memory resources.
 
 :::
 
-To do this, click on any machine you want to edit. Notice the context menu changing, with tabs to add different kinds of
+To do this, click on any machine you want to edit. Notice the simHyperVisorContext menu changing, with tabs to add different kinds of
 units to your machine. Have a look around as to what can be added.
 
 Once you are satisfied with the datacenter design, we will experiment with the design in the next chapter.
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)):