@Test
    public void autoscaling_shouldnt_choose_too_small_disk_compared_to_memory() {
        var min = new ClusterResources(10, 1, new NodeResources(1, 10, 19, 1));
        var now = new ClusterResources(10, 1, new NodeResources(5, 50, 150, 1));
        var max = new ClusterResources(10, 1, new NodeResources(10, 100, 200, 1));
        var fixture = DynamicProvisioningTester.fixture()
                                               .awsProdSetup(true)
                                               .initialResources(Optional.of(now))
                                               .capacity(Capacity.from(min, max))
                                               .build();
        fixture.setScalingDuration(Duration.ofHours(6));
        fixture.tester().clock().advance(Duration.ofDays(2));
        fixture.loader().applyLoad(new Load(0.5, 0.8, 0.1, 0, 0), 120);
        fixture.tester().assertResources("Suggesting resources where disk is 3x memory (this is a content cluster)",
                                         11, 1, 13.9,  60.0,  179.9,
                                         fixture.tester().suggest(fixture.applicationId, fixture.clusterSpec.id(), min, min));
        fixture.tester().assertResources("Autoscaling to resources where disk is 3x memory (this is a content cluster)",
                                         10, 1, 10.0,  66.2,  198.6,
                                         fixture.tester().autoscale(fixture.applicationId, fixture.clusterSpec, Capacity.from(min, max)));
    }
We prefer fewer nodes for container clusters as (we assume) they all use the same disk and memory
node-repository/src/test/java/com/yahoo/vespa/hosted/provision/autoscale/AutoscalingTest.java