8000 Investigate perfomance bottle neck · Issue #401 · tarantool/cartridge-java · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Investigate perfomance bottle neck #401

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
ArtDu opened this issue Jun 14, 2023 · 0 comments
Open

Investigate perfomance bottle neck #401

ArtDu opened this issue Jun 14, 2023 · 0 comments
Assignees
@ArtDu
Labels
customer

Comments

@ArtDu
Copy link
Contributor
ArtDu commented Jun 14, 2023 •
edited
Loading

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:

    cartridge-java/src/test/java/io/tarantool/driver/benchmark/BenchmarkRunner.java

    Lines 70 to 75 in 67c9f67

    TarantoolResult<TarantoolTuple> tuples = plan.tarantoolClient.call(
    "return_arrays_with_different_types",
    Collections.emptyList(),
    plan.defaultMapper,
    plan.resultMapper
    ).join();
@ArtDu ArtDu added the customer label Jun 14, 2023
@ArtDu ArtDu self-assigned this Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ArtDu ArtDu

Labels
customer
Projects
None yet
Milestone
No milestone
3431
Development

No branches or pull requests
1 participant
@ArtDu
0