@kolektiv this trival example should run without issue
module BDNetFSharp.Program
open BenchmarkDotNet
open System.Reflection
type ArrayVsList () =
[<Params (10, 100)>]
member val public ColSize = 0 with get, set
[<Benchmark>]
member self.GetSquareArray () =
let value = self.ColSize / 2 in [| for _ in 0 .. self.ColSize -> value |].[value]
[<Benchmark>]
member self.GetSquareList () =
let value = self.ColSize / 2 in [for _ in 0 .. self.ColSize -> value ].[value]
let [<EntryPoint>] main args =
let competitionSwitch =
Assembly.GetExecutingAssembly().GetTypes()
|> Array.filter (fun t ->
t.GetMethods (BindingFlags.Instance ||| BindingFlags.Public )
|> Array.exists (fun m -> m.GetCustomAttributes (typeof<BenchmarkAttribute>, false) <> [||]))
|> BenchmarkSwitcher
competitionSwitch.Run args
0
@mattwarren, check it out, I added BenchmarkEnvironmentAnalyser: PerfDotNet/BenchmarkDotNet@de01401
@smudge202, I thought that you want to implement CoreCLR support (you even have a local branch with some commits: https://github.com/smudge202/BenchmarkDotNet/commits/features/33-dnx-compatibility) Am I wrong?
@mattwarren, I am ready to publish v0.8.2, there is ChangeLog: https://github.com/PerfDotNet/BenchmarkDotNet/wiki/ChangeLog It includes your recent
Baseline feature. Do you want to commit something before publishing?
BTW I think that the ChangeLog is a really nice idea. It also shows that BenchmarkDotNet is becoming a more mature OSS project, good job!
You have removed my
BenchmarkStatResultExtenderTests and spoil BaselineDeltaResultExtenderTest, PerformanceUnitTest, see diff with parent 140deccc.
Did you manage to fix it, or do you need me to do something?
Yeah, I'll take a look at the develop branch as well
BTW this (me messing up the merge) makes me think that we need some sort of C.I build
I used AppVeyor before, can you access https://ci.appveyor.com/project/mattwarren/minibench-warren and see it?
can you access https://ci.appveyor.com/project/mattwarren/minibench-warren and see it?
Seems that is is a public page, everyone can see it.
I've just pushed the changes so that
new BenchmarkRunner().Run<BenchmarkProgram>(); works when you have a Benchmark with [Benchmark(Baseline = true)]
so you can do the release now if you want
@mattwarren, also, what do you think about new following renaming:
BenchmarkJitVersion -> BenchmarkJitter?
BenchmarkJitVersion->BenchmarkJitter
Yeah makes sense to me. The only issue I see is that "Jitter" has another meaning (https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=jitter) which might confuse things
On a related note, I was thinking, do we need to "Benchmark" prefix everywhere?! I know it would be big change, but within the BenchmarkDotNet source base "Benchmark" is already implied, so in a lot (but not all cases) it's a bit redundant
I have an idea about ResultExtenders. We can transform all of your standard columns (like
Type, Method, Platform, etc.) to ResultExtenders. Then it will not be "extenders". We can call it "BenchmarkColumn". (see also: PerfDotNet/BenchmarkDotNet#82, we can define the column set manually per benchmark).
