If this is purely JavaScript related you can use d8 (the v8 command line
profiler) to do the profiling for you.
I recently added source maps support to it so you can actually profile
obfuscated GWT code just fine.
Here is what you need to do:
1. Build v8 yourself
2. Compile your code using a
Shortly after 2.5.1, the Benchmark classes were removed from GWT
(https://gwt.googlesource.com/gwt/+/39eb6001a037fd8b6580a73a2540e6e9c04e54c2
and
https://gwt.googlesource.com/gwt/+/00c7ce43df3a629b7302ab902a07431db7224e2b)
- what are folks using for low-level performance testing these days?
On Mon, Aug 26, 2013 at 1:47 PM, Colin Alworth niloc...@gmail.com wrote:
Shortly after 2.5.1, the Benchmark classes were removed from GWT (
https://gwt.googlesource.com/gwt/+/39eb6001a037fd8b6580a73a2540e6e9c04e54c2and
The latest benchmarks (before the removal Benchmarks suite) was done by
custom infra:
https://gwt.googlesource.com/gwt/+/master/reference/Microbenchmarks/src/com/google/gwt/reference/microbenchmark
If you would like to collect timing from some previous GWTTestCases you can
do that by overriding
