Is it possible to introduce asynchronous capability in benchmark setup? Right now, it is impossible for me to use GWT benchmarking because of async initialization in my components (e.g. Flash Plugin). There are other reasons one might need an async setup phase, such as the need to perform a network I/O to load real data for the benchmark to act on.
What I really need is a list of all the reasonable use cases for asynchronous behavior in benchmarks, during setup, test, or teardown. Given that, I think we can evolve things such that people are able to achieve what they need to.
Sign in to add a comment
Toby,
Hey Ray,
It looks like you're not alone: http://code.google.com/p/google-web-toolkit/issues/detail?id=2153
Can you add your thoughts to that issue?
What I really need is a list of all the reasonable use cases for asynchronous behavior in benchmarks, during setup, test, or teardown. Given that, I think we can evolve things such that people are able to achieve what they need to.