Skip to content
This repository has been archived by the owner on Dec 7, 2023. It is now read-only.

Investigate and address certain performance problems for high-volume workloads. #84

Open
alexbarcelo opened this issue Oct 29, 2020 · 1 comment

Comments

@alexbarcelo
Copy link
Member

We detected certain misbehaviour when executing numerical applications without active features --i.e. doing attribute getters and attribute setters with big numerical data structures.

At first we assumed that it was some performance penalty at the gRPC or socket/serialization layer, and certain preliminary results seemed to confirm that, but after more in-depth tests the results came up unconclusive.

@alexbarcelo
Copy link
Member Author

alexbarcelo commented Oct 29, 2020

Some experiments backing up the "unconclusiveness":

Getter time
Normalized getter time

(size is in kiB. Goes from 1kiB to 1GiB)

The normalized time seams to plateau, which is an expected well-behaviour. Small rpc have a big overhead, but that can be assumed. For these experiments the base rpc overhead is around $10^{-3}s$.

[Note: The difference between ndarray and numerical_array is implemented in bsc-dom/pyclay/pull/59]

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant