Repository navigation
Add MigrationCheckBenchmark for cloudsimplus#94 - #21
Open
manoelcampos wants to merge 1 commit into
Open
manoelcampos wants to merge 1 commit into
manoelcampos wants to merge 1 commit into
Conversation
Measure the time and memory allocated by one VM migration check (VmPlacementPolicyMigrationAbstract.getOptimizedPlacementMap()) with overloaded, underloaded and half used Hosts, for 100 to 2,000 Hosts. It's the baseline for cloudsimplus#94 and cloudsimplus#648. The README has the results for CloudSim Plus master (4a160b4bb): both time and allocated memory grow quadratically with the number of Hosts (1.8 s and 7.3 GB per check with 2,000 Hosts). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of cloudsimplus/cloudsimplus#94. Related to cloudsimplus/cloudsimplus#648 and cloudsimplus/cloudsimplus#652.
Adds
MigrationCheckBenchmark, a JMH benchmark that measures one VM migration check: a call toVmPlacementPolicyMigrationAbstract.getOptimizedPlacementMap(). It's the baseline to compare against after the #94 refactor, which stops creating and destroying VMs to compute the migration map.Scenario
VmPlacementPolicyMigrationStaticThreshold(thresholds 0.8 and 0.2) withVmSelectionPolicyMinimumUtilization.-prof gcto also get the memory allocated per check.Results on CloudSim Plus
master(4a160b4bb)JDK 25.0.4, JMH 1.35, 1 fork, 5 warmup and 10 measurement iterations of 2 seconds.
Both the time and the memory allocated by a check grow quadratically: doubling the number of Hosts makes a check about 4 times slower and allocate about 4 times more memory.
While #94 isn't fixed, the first check changes the placement: VMs planned to leave underloaded Hosts are left in their target Hosts too, and some VMs are removed from the broker's list of running VMs. The state stops changing after the first check, so the warmup iterations make every measured check start from the same placement. This is documented in the benchmark.
Engineering principles
VmSpecrecord keeps each VM's Host, cores and CPU utilization in one place, used to create both the VM and its Cloudlet🤖 Generated with Claude Code