Hi Jochen,
> hardware is the same for all. afaik the parrot branch under the "JDK 7
> build" is tested with a JDK7 build bot. "Antlr4 grammar" is tested with
> a JDK8 bot. The same bot is used for "JDK 8 build".
If "Antlr4 grammar" is using the same bot with "JDK 8 build", the
performance of Parrot is too good to believe ?? "Antlr4 grammar#180" ran 21591
tests and costed 23m:48s, and “JDK 8 Build#1801” ran 11155 tests and costed
22m:35s. As we can see, they costed almost same time, but "Antlr4 grammar#180"
ran much more tests than “JDK 8 Build#1801”(10436 more tests)...
> BUILD TESTS COUNT COSTED
> TIME
> JDK 8 Build#1801 11155 22m:35s
> Antlr4 grammar#180 21591 23m:48s
Cheers,
Daniel.Sun
发件人: Jochen Theodorou [via
Groovy]<mailto:[email protected]>
发送时间: 2017年1月30日 0:58
收件人: Daniel Sun<mailto:[email protected]>
主题: Re: About the performance of the test builds
On 29.01.2017 15:46, Daniel Sun wrote:
> Hi all,
>
> I noticed that test builds that use JDK 8 cost different time, they run
> tests from master and parrot branch(contains all commits from
> master)(http://ci.groovy-lang.org/project.html?projectId=Groovy), e.g.
>
> BUILD TESTS COUNT COSTED
> TIME
> JDK 8 Build#1801 11155 22m:35s
> JDK 8 snapshot build#995 11155 15m:32s
> Antlr4 grammar#180 21591 23m:48s
>
> Who can tell me what's different among the CI instances of "JDK 8
> Build", "JDK 8 snapshot" and "Antlr4 grammar"?
hardware is the same for all. afaik the parrot branch under the "JDK 7
build" is tested with a JDK7 build bot. "Antlr4 grammar" is tested with
a JDK8 bot. The same bot is used for "JDK 8 build". "JDK 8 snapshot
build" uses a checked out JDK8 to run. If "JDK 8 snapshot" is much
faster, then maybe because of changes the JDK people did for an upcoming
new JDK8 release
> PS:
> If "Antlr4 grammar" CI instance has same hardware resource with "JDK 8
> Build" CI instance, we can say the new parser Parrot has better performance
> than the old one;
> If "Antlr4 grammar" CI instance has same hardware resource with "JDK 8
> snapshot build" CI instance, we can say the new parser Parrot has almost
> same performance with the old one;
If you want to compare performance I suggest you run the build on your
computer with different JDKs. There you have much more control over things
bye Jochen
________________________________
If you reply to this email, your message will be added to the discussion below:
http://groovy.329449.n5.nabble.com/About-the-performance-of-the-test-builds-tp5738218p5738219.html
To unsubscribe from About the performance of the test builds, click
here<http://groovy.329449.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=5738218&code=cmVhbGJsdWVzdW5AaG90bWFpbC5jb218NTczODIxOHwxMTQ2MjE4MjI1>.
NAML<http://groovy.329449.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
View this message in context:
http://groovy.329449.n5.nabble.com/About-the-performance-of-the-test-builds-tp5738218p5738220.html
Sent from the Groovy Dev mailing list archive at Nabble.com.
