ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Kuznetsov (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (IGNITE-7531) SQL: Create data load benchmarks
Date Tue, 06 Feb 2018 14:32:00 GMT

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

Pavel Kuznetsov edited comment on IGNITE-7531 at 2/6/18 2:31 PM:
-----------------------------------------------------------------

*Extend Yardstick capabilities*

I found next solution:
1) Run benchmarks with {{--warmup 0 --operations 1}} to run {{test()}} method single time
and don't run it during warmup
2) Perform custom warmup (insert fewer amount of data) in {{setUp()}} method
 


was (Author: pkouznet):
*Extend Yardstick capabilities*

I found next solution:
1) Run benchmarks with {{--warmap 0 --operations 1}} to run {{test()}} method single time
and don't run it during warmup
2) Perform custom warmup (insert fewer amount of data) in {{setUp()}} method
 

> SQL: Create data load benchmarks
> --------------------------------
>
>                 Key: IGNITE-7531
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7531
>             Project: Ignite
>          Issue Type: Task
>          Components: sql, yardstick
>            Reporter: Vladimir Ozerov
>            Assignee: Pavel Kuznetsov
>            Priority: Major
>             Fix For: 2.5
>
>
> We need to implement a set of data loading benchmarks to better understand how fast Ignite
is able to consume data. This task consists of two steps:
> 1) Extend Yardstick capabilities
> 2) Create set of benchmarks
> 1) Yardstick
> Data load benchmark should be executed in single-shot mode: only one iteration, only
total execution time is needed, start callback for setup and warmup, stop callback for cleanup.

> Currently Yardstick cannot do that, so we need to extend it. Possibly, we can control
this through new {{boolean BenchmarkDriver.isSingleShot()}} method.
> 2) Benchmarks 
> At first let's focus on thin JDBC driver. The following cases should be executed:
> 2.1) Normal INSERT
> 2.2) Batched INSERT
> 2.3) Streaming INSERT (when IGNITE-7253 is ready)
> 2.4) P. 1-3 with and without dynamically disabled WAL (ALTER TABLE ... NOLOGGING)
> 2.5) P. 1-3 with additional indexes - either created before data load on empty table,
or after load on table with data.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message