to collect timing from some previous GWTTestCases you
can do that by overriding some base methods on GWTTestcase (runBare
includes gwtSetup and doRunTest does not) and log the timings.
PS: Old benchmark suite was a hack over GWTTestCase infra that was adding
a lot of complexity without much
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
https://gwt.googlesource.com/gwt/+/00c7ce43df3a629b7302ab902a07431db7224e2b
some base methods on GWTTestcase (runBare includes
gwtSetup and doRunTest does not) and log the timings.
PS: Old benchmark suite was a hack over GWTTestCase infra that was adding a
lot of complexity without much benefit.
On Mon, Aug 26, 2013 at 11:16 AM, John A. Tamplin j...@jaet.org wrote
Did anybody try this on practice
http://code.google.com/p/google-web-toolkit/wiki/LightweightCollections?
Would be interested to see the results in real life project.
On Sep 30, 12:00 am, jhulford jhulf...@gmail.com wrote:
They already have addressed
On Sep 30, 2:16 pm, Slava Lovkiy slava.lov...@gmail.com wrote:
Did anybody try this on
practicehttp://code.google.com/p/google-web-toolkit/wiki/LightweightCollections?
Would be interested to see the results in real life project.
The code is here:
They already have addressed it:
http://code.google.com/p/google-web-toolkit/wiki/LightweightCollections
As far as I know, there's no set release for the code though.
On Sep 28, 9:55 am, Fernando spiderkens...@gmail.com wrote:
very interesting, even more if coupled with this one (read it
very interesting, even more if coupled with this one (read it
yesterday):
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/d20b0d9cad299223
imho, GWT Team should address to these performance issues as soon as
they have the time
if we're going to use Java on a daily basis
Not sure if it was posted before but I found following interesting
blog about GWT Array performance:
http://lgrammel.blogspot.com/2010/09/gwt-arraylist-hashset-and-jsarray.html
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to
The second part of my benchmark is out now, with figures from Windows
XP, Chromium OS, Android, Symbian OS
http://bit.ly/aYqWAo
On Jul 26, 4:38 pm, Ciarán ciaran.mccann@gmail.com wrote:
Hey everyone I am really interested in GWT for a project I am working
at the moement. The main benefit
am working
at the moement. The main benefit for me is the fact that I don't have
to write JavaScript which I really dislike, but then I was thinking
would the code produced by GWT be slower then hand crafted JavaScript
so I ran a benchmark, the results of which I posted herehttp://bit.ly/cxo4dS
a benchmark, the results of which I posted here http://bit.ly/cxo4dS
some very interesting results when running it on the iphone.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-tool
Hey everyone I am really interested in GWT for a project I am working
at the moement. The main benefit for me is the fact that I don't have
to write JavaScript which I really dislike, but then I was thinking
would the code produced by GWT be slower then hand crafted JavaScript
so I ran a benchmark
Revision: 8301
Author: rchan...@google.com
Date: Mon Jun 14 11:58:23 2010
Log: Optimized MutableArray creation. Added Benchmark to facilitate
comparison using a single graph.
Review at http://gwt-code-reviews.appspot.com/613801
Review by: r...@google.com
http://code.google.com/p/google-web
http://gwt-code-reviews.appspot.com/547801/show
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
LGTM
http://gwt-code-reviews.appspot.com/547801/show
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Revision: 8212
Author: rchan...@google.com
Date: Wed May 26 04:38:31 2010
Log: Added benchmark task to ant in user/
Review at http://gwt-code-reviews.appspot.com/547801
Review by: sp...@google.com
http://code.google.com/p/google-web-toolkit/source/detail?r=8212
Added:
/branches/2.1/user/test
http://gwt-code-reviews.appspot.com/547801/show
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
http://gwt-code-reviews.appspot.com/547801/show
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
http://gwt-code-reviews.appspot.com/547801/diff/5001/6003
File /user/build.xml (right):
http://gwt-code-reviews.appspot.com/547801/diff/5001/6003#newcode664
/user/build.xml:664: unless=test.web.remote.disable
This should rather be benchmark.web.remote.disable
/
This looks too tricky. Is it here so that the benchmark targets can
depend on various targets, and yet prevent those targets from actually
building? If so, why not simply depend on more specifically what the
targets require to be built?
If the existing ant targets are too coarse, then they can certainly
Reviewers: Lex,
Description:
Added benchmark task to ant in user/
Please review this at http://gwt-code-reviews.appspot.com/547801/show
Affected files:
M /build.xml
M /common.ant.xml
M /user/build.xml
A /user/test/com/google/gwt/emultest/EmulSuiteBenchmark.java
A /user/test/com
Committed r7357
http://gwt-code-reviews.appspot.com/127801
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
Picked up last rounds of feedback from Joel (EmptyBinder weirdness),
Thomas and James. Also checkstyle fixes.
Barring further objections, I'll submit this in the morning. There are
more tests that could be implemented (Joel may have written them
already), but I'd like to get in what I have.
SGTM. I've got more to add once it's in.
On Mon, Jan 4, 2010 at 8:29 PM, rj...@google.com wrote:
Picked up last rounds of feedback from Joel (EmptyBinder weirdness),
Thomas and James. Also checkstyle fixes.
Barring further objections, I'll submit this in the morning. There are
more tests
DivElement detachedDiv =
Document.get().createDivElement();
Isn't this creating a clinit, when accessing TestDom.HTML from other
widgets (e.g. TestCursorDomCrawl).
Shouldn't make much of a difference on the benchmark results but
still...
http://gwt-code-reviews.appspot.com/127801/diff/1101/1117
File
= System.currentTimeMillis();
For a time sensitive benchmark framework, I snub my nose at looping in
the long emulation. Why not just have a simple private utility method:
private static native double currentTimeMillis() /*-{
return (new Date()).getTime();
}-*/;
http://gwt-code
force a layout by measuring the offsetTop of the
bottom-most widget I create. This won't capture paint, but layout seems
to be the real monster most of the time.
One comment on the structure of the benchmark: It's a little confusing
to see a bunch of measurements on things that create *different
Thanks, Joel. The intent here is that the resulting structures are as
near identical as I can make them. Did you see something else?
http://gwt-code-reviews.appspot.com/127801
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
them to the test cases.
http://gwt-code-reviews.appspot.com/127801/diff/1101/1116#newcode178
Line 178: long start = System.currentTimeMillis();
On 2009/12/22 19:38:26, jaimeyap wrote:
For a time sensitive benchmark framework, I snub my nose at looping in
the long
emulation. Why not just have
http://gwt-code-reviews.appspot.com/127801/diff/1101/1106
File
reference/Microbenchmarks/src/com/google/gwt/reference/microbenchmark/client/Microbenchmarks.java
(right):
http://gwt-code-reviews.appspot.com/127801/diff/1101/1106#newcode59
Line 59: horizontalPanel.remove(runningLabel);
Here is a
The IE bug was actually due to using span/ instead of span/span in
the innerHTML (and appears to have been fixed in IE8.
I've fixed the timing so that it now includes layout. I used Joel's
trick of calling getOffsetTop rather than setTimeout(0) so that I could
keep the code synchronous.
Also
Oh, and the punchline: crawling is still consistently winning, maybe
even more so now that I'm forcing layout.
http://gwt-code-reviews.appspot.com/127801
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
/JettyLauncher.java
dev/core/src/com/google/gwt/dev/util/BrowserLauncher.java
tools/benchmark-viewer/src/com/google/gwt/benchmarks/viewer/server/ReportXml.java
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
LGTM with a nit - I only reviewed the JettyLauncher change.
http://gwt-code-reviews.appspot.com/120801/diff/1/4
File dev/core/src/com/google/gwt/dev/shell/jetty/JettyLauncher.java
(right):
http://gwt-code-reviews.appspot.com/120801/diff/1/4#newcode479
Line 479: private TreeLogger.Type
Revision: 7289
Author: j...@google.com
Date: Wed Dec 9 16:06:06 2009
Log: Fix benchmark viewer.
Patch by: jat
Review by: tobyr, rdayal
http://code.google.com/p/google-web-toolkit/source/detail?r=7289
Added:
/trunk/dev/core/src/com/google/gwt/dev/RunWebApp.java
Modified:
/trunk/dev/core/src
Hi there,
I found benchmark handy to measure the capabilities of the app I was
working on. I just wondered how it (or generally gwt unit test) is
going to work with oophm in 2.0. Is it able to run in browsers with
plug-in installed or still in the current way? Please shed some light
Author: sco...@google.com
Date: Wed Apr 8 18:21:02 2009
New Revision: 5201
Modified:
trunk/eclipse/tools/benchmark-viewer/.classpath
Log:
Fixed bad classpath in benchmark-viewer project.
Modified: trunk/eclipse/tools/benchmark-viewer/.classpath
Author: sco...@google.com
Date: Wed Mar 11 11:39:23 2009
New Revision: 4984
Added:
releases/1.6/tools/benchmark-viewer/war/gradient.gif
- copied unchanged from r4978,
/releases/1.6/tools/benchmark-viewer/src/com/google/gwt/benchmarks/viewer/public/gradient.gif
Removed
Author: sco...@google.com
Date: Tue Mar 10 18:53:38 2009
New Revision: 4981
Added:
releases/1.6/eclipse/tools/benchmark-viewer/ReportViewer-gwtc.launch
releases/1.6/eclipse/tools/benchmark-viewer/ReportViewer.launch
Log:
Adding launch configs for benchmark viewer.
Added: releases/1.6
Author: sco...@google.com
Date: Tue Mar 10 19:16:02 2009
New Revision: 4982
Modified:
releases/1.6/tools/benchmark-viewer/build.xml
Log:
Fixed wrong default build rule.
Modified: releases/1.6/tools/benchmark-viewer/build.xml
Author: sco...@google.com
Date: Tue Mar 3 21:04:17 2009
New Revision: 4916
Added:
releases/1.6/eclipse/tools/benchmark-viewer/.checkstyle
Modified:
releases/1.6/eclipse/tools/benchmark-viewer/.project
releases/1.6/tools/benchmark-viewer/src/com/google/gwt/benchmarks/viewer/client
42 matches
Mail list logo
