diff options
| author | Aria <me@aria.rip> | 2023-10-20 18:39:57 +0100 |
|---|---|---|
| committer | Aria <me@aria.rip> | 2023-10-20 18:39:57 +0100 |
| commit | 5c318dbaf86747c8b054835f066717c5a30911c5 (patch) | |
| tree | 3ac3444b7cbf3f9b41a70d869b2f6ec95f71a6d1 /thesis/parts/background.tex | |
| parent | da823974b3e417bef457e26c49113f90f1075be1 (diff) | |
minor grammar
Diffstat (limited to 'thesis/parts/background.tex')
| -rw-r--r-- | thesis/parts/background.tex | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/thesis/parts/background.tex b/thesis/parts/background.tex index a0326df..77becd6 100644 --- a/thesis/parts/background.tex +++ b/thesis/parts/background.tex @@ -148,8 +148,8 @@ As we note above, this scales poorly. We aim to create a container selection method that addresses both functional and non-functional requirements in a scalable way. Primrose will be used as the first step, in order to select candidates based on functional requirements. -We will then collect statistics from user-provided benchmarks, and create cost estimates for each candidate, similar to CollectionSwitch. -Unlike CollectionSwitch, this will be done offline, rather than as the program is running. +We will then collect statistics from user-provided benchmarks and create cost estimates for each candidate, similarly to CollectionSwitch. +Unlike CollectionSwitch, this will be done offline rather than as the program is running. This will provide an integrated and flexible solution that addresses both functional and non-functional requirements. We believe no such solution exists in current literature. |