[jira] [Commented] (QUICKSTEP-23) Add a performance CI to the development workflow

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/QUICKSTEP-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331422#comment-15331422 ] 

ASF GitHub Bot commented on QUICKSTEP-23:
-----------------------------------------

Github user pateljm commented on the issue:

    https://github.com/apache/incubator-quickstep/pull/33
  
    This also points out that we should have a better CI in place for performance testing. We periodically run benchmark tests, but that is not in a CI pipeline. Travis is not ideal for this (no guarantees on the underlying VM that is created), but there are tools like [blitz.io](https://www.blitz.io/)  and [blazemeter](https://www.blazemeter.com/) that could work. Added a [JIRA ticket](https://issues.apache.org/jira/browse/QUICKSTEP-23) to make a note of this.


> Add a performance CI to the development workflow
> ------------------------------------------------
>
>                 Key: QUICKSTEP-23
>                 URL: https://issues.apache.org/jira/browse/QUICKSTEP-23
>             Project: Apache Quickstep
>          Issue Type: Improvement
>            Reporter: Jignesh Patel
>            Priority: Minor
>
> High performance is a crucial goal for the project, but we don't have a good way of adding large performance tests to our CI pipeline. What is needed is to add a benchmark on some significant amount of data (ideally multiple GB or more) and an underlying hardware with significant multi-core/socket parallelism. 
> Note adding a benchmark to the existing Travis pipeline is not a viable solution as there are no guarantees about the the underlying VM that is created. 
> Explore other solutions that may work, including blitz.io (https://www.blitz.io/)  and BlazeMeter (https://www.blazemeter.com/).
> A good target is: SSB or TPC-H at 10SF on a 4-core or better. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)