This sounds great.
Since every language has a benchmarking tool, we can start with JMH and
expand from there.
A key point is that we will want to dedicate a Jenkins machine exclusively
to this when the microbenchmarks are running, otherwise we will have other
competing Jenkins jobs using up CPU t
Sorry Robert, I should have mentioned … that’s the Java Microbenchmark Harness.
So this is all about the Java SDK. Currently there’s benchmarks for the
fn-harness and some benchmarks for core are in progress.
Cheers
On 12.07.22, 17:50, "Robert Burke" wrote:
I'm all for additional performance b
I'm all for additional performance benchmarks!
But what does JMH stand for?
On Tue, Jul 12, 2022, 7:54 AM Moritz Mack wrote:
> Hi all,
>
>
>
> This is a very short proposal to start running JMH benchmarks periodically
> and store benchmark results so we can start monitoring performance trends
>
Hi all,
This is a very short proposal to start running JMH benchmarks periodically and
store benchmark results so we can start monitoring performance trends on the
community metrics dashboards over time. Comments most welcome!
https://s.apache.org/nvi9g
Best regards,
Moritz
As a recipient of
Maybe Kenn and I need to sign in?
>
> I think I see what's going on. When I hit
> https://s.apache.org/beam-community-metrics-infra I see a list of
> "Recently viewed dashboards" which you won't have on first pageview.
>
> To see the available dashboards and naviga
> Also blank for me. Maybe Kenn and I need to sign in?
I think I see what's going on. When I hit
https://s.apache.org/beam-community-metrics-infra I see a list of "Recently
viewed dashboards" which you won't have on first pageview.
To see the available dashboards and nav
> I previously wrote a page for the wiki:
> https://cwiki.apache.org/confluence/display/BEAM/Community+Metrics . I
> chose the wiki over website because Community Metrics is Beam
> contributor-focused (as opposed to for Beam users), and not tied to a
> release. If it would fit better
> I think it would be good to have a build infra section under
https://beam.apache.org/contribute/ that contains the dashboard link and
other related information.
I previously wrote a page for the wiki:
https://cwiki.apache.org/confluence/display/BEAM/Community+Metrics . I
chose the wiki o
work done this summer by Mikhail,
>> > Udi, and Huygaa to visualize and track some project/community health
>> > metrics for Beam. Specifically, they've helped to build dashboards for:
>> > * Test suite health (pre-commit speed, post-commit reliability)
>> > *
liability)
> > * Pull Request health (code review latency, PR load per reviewer)
> >
> > Check it out here: https://s.apache.org/beam-community-metrics, and
> > please leave feedback on this thread or under our umbrella JIRA item:
> > BEAM-5862.
> >
> > Th
ode review latency, PR load per reviewer)
Check it out here: https://s.apache.org/beam-community-metrics, and
please leave feedback on this thread or under our umbrella JIRA item:
BEAM-5862.
There's some new infrastructure behind this which is hosted alongside
our Jenkins resources on Google C
ealth (code review latency, PR load per reviewer)
Check it out here: https://s.apache.org/beam-community-metrics, and please
leave feedback on this thread or under our umbrella JIRA item: BEAM-5862.
There's some new infrastructure behind this which is hosted alongside our
Jenkins resources
12 matches
Mail list logo
