Return-Path: X-Original-To: apmail-ignite-issues-archive@minotaur.apache.org Delivered-To: apmail-ignite-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4A80B19A7B for ; Thu, 14 Apr 2016 06:57:26 +0000 (UTC) Received: (qmail 76618 invoked by uid 500); 14 Apr 2016 06:57:26 -0000 Delivered-To: apmail-ignite-issues-archive@ignite.apache.org Received: (qmail 76535 invoked by uid 500); 14 Apr 2016 06:57:26 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 76502 invoked by uid 99); 14 Apr 2016 06:57:25 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 14 Apr 2016 06:57:25 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 9C1BC2C1F68 for ; Thu, 14 Apr 2016 06:57:25 +0000 (UTC) Date: Thu, 14 Apr 2016 06:57:25 +0000 (UTC) From: "Denis Magda (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (IGNITE-2952) Add yardstick benchmark for cache load testing MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IGNITE-2952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denis Magda updated IGNITE-2952: -------------------------------- Affects Version/s: 1.5.0.final > Add yardstick benchmark for cache load testing > ---------------------------------------------- > > Key: IGNITE-2952 > URL: https://issues.apache.org/jira/browse/IGNITE-2952 > Project: Ignite > Issue Type: Test > Affects Versions: 1.5.0.final > Reporter: Semen Boikov > Assignee: Vladislav Pyatkov > > Need implement yardstick benchmark which will be used for cache load testing (add it in 'yardstick' module). > For this load testing nodes will be started with several pre-configured caches. Benchmark on each call of 'test' method should iterate over all configured caches (can get list of caches using Ignite.cacheNames) and execute some random operations: > - put(All) > - get(All) > - invoke(All) > - remove(All) > - putIfAbsent > - replace > - scan query > If cache is transactional it also should execute cache operations inside explicitly start transaction with random concurrency/isolation mode. > This benchmark can be run in scenario when server nodes are restarted, so for explicit transaction need use method IgniteBenchmarkUtils.doInTransaction which has logic for exception handling. > It should be possible to pre-load some cache data before starting test , there should be special benchmark parameter which specifies how many entries load in caches on start (see IgniteSqlQueryBenchmark.setUp as example of benchmark doing preloading) > Also it should use non-primitives objects as cache keys/values. Value class should have String, int, long, double, byte[] fields. -- This message was sent by Atlassian JIRA (v6.3.4#6332)