Native needs the Level configuration

[CharlieTap]

Without being able to specify level iteration, tests are really clunky to configure. For example say I have a class:

class Benchmark {

    val stack = stack()

    @Setup
    fun setup() {
        stack.push(1)
    }
 
    @Teardown
    fun cleanup() {
         stack.clear()
    }


    @Benchmark
    fun benchmark() {
        stack.pop()
    }
}

This will not work because setup is only ran once. I could push a 1000 elements during setup and just hope the iterations exceed the amount of pops in the test, but this would also mean stack has an unrealistically large dataset and skew my measurement. I could put the setup code in the actual benchmark itself, but then I wouldn't be measuring exactly what I want. Level is a really important important config in JMH and without it native tests seem too awkward to be worth configuring

[deep4nsh]

@CharlieTap you can try this

class Benchmark {

val stack = stack()

@Setup(Level.Iteration)
fun setup() {
    stack.push(1)  // This runs for each iteration
}

@Teardown(Level.Iteration)
fun cleanup() {
     stack.clear()  // This clears after each iteration
}

@Benchmark
fun benchmark() {
    stack.pop()  // This runs every time a benchmark iteration is executed
}

}

[fzhinkin]

@deep4nsh kotlinx-benchmark does not provide Level, nor its Setup and TearDown annotations accept parameters.

[deep4nsh]

@fzhinkin i could find for this solution.

import org.jetbrains.kotlin.benchmark.Benchmark
import org.jetbrains.kotlin.benchmark.Setup
import org.jetbrains.kotlin.benchmark.TearDown

class Benchmark {

val stack = mutableListOf<Int>()

@Setup
fun setup() {
    stack.push(1)
}

@TearDown
fun cleanup() {
    stack.clear()
}

@Benchmark
fun benchmark() {
    stack.pop()
}

}

fun benchmark() {
stack.clear()
stack.push(1)
stack.pop()
}