I analyzed the performance of POST: /{token_address}/TransferHistory/Search. As a result, it was found that the response time increased as the size of the input list of account addresses increased.
I have investigated that there are no problems with SQL latency and SQL execution plans.
My analysis results show that the rate of response degradation varies depending on the token. The cause of this is currently unknown.
In any case, the performance deterioration is noticeable as the number of accounts managed by the wallet increases, so I think it is necessary to consider other ways to filter accounts.
Describe the bug
Related to #1441
I analyzed the performance of
POST: /{token_address}/TransferHistory/Search. As a result, it was found that the response time increased as the size of the input list of account addresses increased.I have investigated that there are no problems with SQL latency and SQL execution plans.
My analysis results show that the rate of response degradation varies depending on the token. The cause of this is currently unknown.
In any case, the performance deterioration is noticeable as the number of accounts managed by the wallet increases, so I think it is necessary to consider other ways to filter accounts.