Skip to content

Investigate perfomance bottle neck  #401

@ArtDu

Description

@ArtDu

We have a case when the connector slows overall request performance with space.select/insert/replace methods.
We've seen that CPU in Java application achieves the ceil, but Tarantool could achieve more.
In my opinion, we can add a test in jmh that creates mapper for each request like it is in space.select:

  1. One instance
  2. Empty call with massive response
  3. Recreating the mapper for each request
    Ref:
    TarantoolResult<TarantoolTuple> tuples = plan.tarantoolClient.call(
    "return_arrays_with_different_types",
    Collections.emptyList(),
    plan.defaultMapper,
    plan.resultMapper
    ).join();

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions