[
https://issues.apache.org/jira/browse/BEAM-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16451915#comment-16451915
]
Łukasz Gajowy commented on BEAM-3456:
-------------------------------------
I would say with a clear conscience that the results improved if there weren't
some peaks since April 22:
[https://apache-beam-testing.appspot.com/explore?dashboard=5755685136498688]
(chart at the very bottom). Nevertheless, straight after the PR was merged the
test runtime decreased a bit. Let's observe that a little longer - the JDBC tst
is still flaky due to connection problems - this is why there are not as many
test results on the char as one would expect (the failed ones are not drawn on
the chart).
> Enable large scale JdbcIOIT Performance Test
> --------------------------------------------
>
> Key: BEAM-3456
> URL: https://issues.apache.org/jira/browse/BEAM-3456
> Project: Beam
> Issue Type: Bug
> Components: testing
> Reporter: Łukasz Gajowy
> Assignee: Łukasz Gajowy
> Priority: Major
> Fix For: 2.4.0
>
> Time Spent: 4h 10m
> Remaining Estimate: 0h
>
> We should use numberOfRecords pipelineOption in Jdbc performance test and
> enable jenkins for it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
