You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Alexander Lapin (Jira)" <ji...@apache.org> on 2022/08/23 08:30:00 UTC

[jira] [Updated] (IGNITE-17410) Implement YCSB benchmark for key-value API

     [ https://issues.apache.org/jira/browse/IGNITE-17410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Lapin updated IGNITE-17410:
-------------------------------------
    Labels: ignite-3 ignite3_performance  (was: ignite-3)

> Implement YCSB benchmark for key-value API
> ------------------------------------------
>
>                 Key: IGNITE-17410
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17410
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Kirill Gusakov
>            Priority: Major
>              Labels: ignite-3, ignite3_performance
>
> We need to have the separate YCSB benchmark for key-value API. Because:
>  * this API is also one of our main API and should be benchmarked too.
>  * it can have the different hotspots comparing to SQL API
>  * it can help us to localize the benchmark issues faster, because key-value API is a kind of lower level API by design



--
This message was sent by Atlassian Jira
(v8.20.10#820010)