We saw that the strategy MultiWalletMultiTable was prepared in the code but not yet implemented.
So decided to do that because we experienced some major peformance issues with the implemented strategies so far.
In addition we added another Strategy: MultiWalletSplitDatabaseMultiTable which cluster the tables in different databases depending on the id of the wallet. That lead to a performance boost.
All unit test ran successfull and we tested the strategy in production aswell but we still consider it as experimentall because further tests are required to ensure that there are no undetected misconceptions.
We saw that the strategy MultiWalletMultiTable was prepared in the code but not yet implemented.
So decided to do that because we experienced some major peformance issues with the implemented strategies so far.
In addition we added another Strategy: MultiWalletSplitDatabaseMultiTable which cluster the tables in different databases depending on the id of the wallet. That lead to a performance boost.
All unit test ran successfull and we tested the strategy in production aswell but we still consider it as experimentall because further tests are required to ensure that there are no undetected misconceptions.
Signed-off-by: j.henrich@esatus.com