This is a placeholder for performance/load testing for dFlow and supporting environments (toB, Ledger).
We have noticed that the system tends to respond slowly to requests that involve querying data coming from the ledger and the agents. We need a way of testing performance, determining possible bottlenecks and addressing the root cause to increase usability.
Example: the call to the /get-credential-dependencies call (that can be issued against any of the running von-x agents), seems to often take more than 30 seconds to complete, incurring in the default timeout time for http requests. While it may be possible to increase the timeout, it would not be a good solution since taking a very long time to complete the request that will indicate the steps that are required to obtain a specific credential reduces the usability of the system.
In addition to ensuring requests are handled correctly in dFlow, we should investigate the underlying back-end layers (von-x, ToB, Ledger) and identify improvements.
This is a placeholder for performance/load testing for dFlow and supporting environments (toB, Ledger).
We have noticed that the system tends to respond slowly to requests that involve querying data coming from the ledger and the agents. We need a way of testing performance, determining possible bottlenecks and addressing the root cause to increase usability.
Example: the call to the
/get-credential-dependencies
call (that can be issued against any of the running von-x agents), seems to often take more than 30 seconds to complete, incurring in the default timeout time for http requests. While it may be possible to increase the timeout, it would not be a good solution since taking a very long time to complete the request that will indicate the steps that are required to obtain a specific credential reduces the usability of the system.In addition to ensuring requests are handled correctly in dFlow, we should investigate the underlying back-end layers (von-x, ToB, Ledger) and identify improvements.