kotlinx-benchmark icon indicating copy to clipboard operation
kotlinx-benchmark copied to clipboard

Kotlin multiplatform benchmarking toolkit

Results 115 kotlinx-benchmark issues
Sort by recently updated
recently updated
newest added
trafficstars

The current README.md references a non-existent document for contribution guidelines. To address this, we need to create a comprehensive document on contribution guidelines inspired by the best practices observed in...

improve documentation

Introduces the capability for users to specify the desired JMH profiler directly as an advanced config option. `advanced("jmhProfiler", "gc")` Resolves: #50

enhancement

Introduces a suite of integration tests to validate the behavior of various configuration options. Aims to ensure that the toolkit behaves as expected when the build script is modified.

tests

Revamped the `AnnotationsSpecifier` class and added tests for multiplatform supported annotations.

tests

All build scripts have been migrated to make use of the most recent DSL versions.

enhancement

(Spin-off from the #176) When working on performance improvements, sometimes there's a need to validate performance with different runtime versions. It would be nice to support per-configuration runtime version selection....

enhancement

Currently, Gradle tasks executing benchmarks don't fail if some benchmarks fail. That might not be a problem if benchmarks are executed within the IDE, as failure status will be reported...

Sample projects are meant to showcase the library features and possible configurations. Current [example projects](https://github.com/Kotlin/kotlinx-benchmark/tree/master/examples) do not cover all of them. Introduce sample projects for: - [ ] Kotlin Mutiplatform...

improve documentation

Currently, there's no way to configure a set of options to pass to a runtime when executing benchmarks. There are several use cases when it could be useful: - running...

enhancement

During the warmup phase, the native benchmarks executor estimates the repetitions of benchmarked function calls within each measurement iteration. That number is stored in an integer variable. Given a fast...

bug