Skip to content

feat(sdk): reuse dapi connections - #1815

Merged
QuantumExplorer merged 2 commits into
v1.0-devfrom
feat/dapi-client-connection-pool
Apr 13, 2024
Merged

feat(sdk): reuse dapi connections#1815
QuantumExplorer merged 2 commits into
v1.0-devfrom
feat/dapi-client-connection-pool

Conversation

@lklimek

@lklimek lklimek commented Apr 12, 2024

Copy link
Copy Markdown
Contributor

Issue being fixed or feature implemented

We establish new connection to DAPI for every request. This has significant impact on performance.

What was done?

Implemented connection pool that allows reuse of clients.

At his point, the connection pool uses LRU (least-recently used) algorithm to evict unused peers.

How Has This Been Tested?

  1. Run rs-sdk tests in network mode.
  2. Tested on testnet using load_test from rs-platform-explorer.

Breaking Changes

None

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have added "!" to the title and described breaking changes in the corresponding section if my code contains any
  • I have made corresponding changes to the documentation if needed

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

@lklimek lklimek changed the title feat(dapi-client): reuse dapi connections feat(sdk): reuse dapi connections Apr 12, 2024
@QuantumExplorer
QuantumExplorer merged commit 8a61c85 into v1.0-dev Apr 13, 2024
@QuantumExplorer
QuantumExplorer deleted the feat/dapi-client-connection-pool branch April 13, 2024 12:18
@lklimek
lklimek restored the feat/dapi-client-connection-pool branch April 15, 2024 08:31
@shumkov
shumkov deleted the feat/dapi-client-connection-pool branch August 25, 2024 08:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants