Skip to content

integritee-network/worker

Folders and files

NameName
Last commit message
Last commit date

Latest commit

5df0a13 · Jan 17, 2024
Apr 24, 2020
Dec 17, 2023
Jan 17, 2024
Oct 4, 2022
Jan 15, 2024
Jan 17, 2024
Jan 17, 2024
Dec 17, 2023
Oct 6, 2022
Jan 17, 2024
Apr 18, 2019
Sep 15, 2023
Jan 3, 2023
Jun 16, 2023
Aug 14, 2023
Jan 17, 2024
Jan 17, 2024
Jul 17, 2023
Apr 18, 2019
Apr 18, 2019
Nov 8, 2022
Sep 28, 2022
Jan 17, 2024
Jan 15, 2024
Oct 26, 2023
Aug 29, 2023
Aug 29, 2023
Apr 16, 2019
Nov 14, 2023
Sep 15, 2022
Nov 8, 2022
Nov 14, 2023
Oct 13, 2021
Sep 2, 2021
Nov 8, 2022
Jul 26, 2021

Repository files navigation

integritee-worker

Integritee worker for Integritee node or parachain

This is part of Integritee

Build and Run

Please see our Integritee Book to learn how to build and run this.

To start multiple worker and a node with one simple command: Check out this README.

Docker

See docker/README.md.

Tests

There are 3 types of tests:

  • cargo tests
  • enclave tests
  • integration tests

Cargo Tests

Run

cargo test

Enclave Tests

Run

make
./bin/integritee-service test --all

Integration Tests

See docker/README.md

Direct calls scalability

For direct calls, a worker runs a web-socket server inside the enclave. An important factor for scalability is the transaction throughput of a single worker instance, which is in part defined by the maximum number of concurrent socket connections possible. On Linux by default, a process can have a maximum of 1024 concurrent file descriptors (show by ulimit -n). If the web-socket server hits that limit, incoming connections will be declined until one of the established connections is closed. Permanently changing the ulimit -n value can be done in the /etc/security/limits.conf configuration file. See this guide for more information.