[
https://issues.apache.org/jira/browse/IGNITE-8513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16489596#comment-16489596
]
Pavel Kuznetsov commented on IGNITE-8513:
-----------------------------------------
https://github.com/gridgain/apache-ignite/pull/95
> SQL: Write benchmarks to compare mvcc on/off
> --------------------------------------------
>
> Key: IGNITE-8513
> URL: https://issues.apache.org/jira/browse/IGNITE-8513
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Pavel Kuznetsov
> Assignee: Pavel Kuznetsov
> Priority: Major
>
> We need to compare performance with mvcc turned on and off.
> Development branch is ignite-4191
> Scope
> All benchmarks uses native sql api cache.query(SqlFieldsQuery)
> We are using simplified data model: table containing long PK and 1 long value
> field.
> 1) Measure increased load of messages.
> 1 client node and many (4) server nodes.
> Benchmark performs updates in single thread.
> backups = 0, 2
> 2) Measure contention on mvcc processor.
> Many client nodes (4) and 1 server node.
> Benchmark performs updates in many threads. Threads use keys from *disjoint*
> ranges.
> backups = 0
> 3) Measure contention on updates.
> 4 client nodes and 2 server nodes.
> Benchmark performs updates in many threads. Thread use keys from
> *intersecting* ranges.
> Exceptions due to write conflicts should be just ignored.
> Update keys should be sorted to prevent dead locks in current implementation.
> backups = 0
> Common parameters:
> atomicity mode = transactional
> cache mode = partitioned
> persistence = off
> some benchmark code can be reused from IGNITE-7988
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
