Benchmark compare to Tomorrowland

[lilyball]

Could you add Tomorrowland to the benchmarks? I'm curious how it stacks up, since Tomorrowland uses atomics internally instead of locks/queues.

I'd also love to see your benchmark methodology. I see benchmarks for Promises in the repo, but no information on how you collected numbers for the other frameworks.

[shoumikhin]

Sure, feel free to provide corresponding code snippets for our Objective-C and Swift performance tests that would use Tomorrowland instead. We're happy to run them and provide the results. Methodology is fairly simple: we ran each test individually on a device several times, then find the average.

[lilyball]

Ok I've ported your performance tests to Tomorrowland: Gist.

[lilyball]

Incidentally it might be nice to have a performance test that tests how the promise performs when under heavy contention from multiple threads (e.g. adding observers from multiple threads simultaneously). A bit esoteric use-case to be sure, but still interesting.

[shoumikhin]

That kind of test case may be useful, feel free to contribute!
Below are some quick numbers for Tomorrowland-ObjC I see:

1 chained then: 0.000031538
2 chained then: 0.000039722
3 chained then: 0.000044663

[lilyball]

You closed this issue but https://github.com/google/promises/blob/master/g3doc/index.md#benchmark still doesn't list Tomorrowland.

[shoumikhin]

Hi Kevin, we're currently exploring Attabench and other similar platforms to run performance tests automatically and independently, so will follow up once that's ready.