You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've already seen that those indexes have some impact on insertion times adding 30s to the performance test on the worst case. We need now to investigate if there is real gain on other operations which are essentially reads (in contrast to the aggregation performance test which is biased to data insertion times).
Produce performance tests biased to data read
Run tests with the indexes proposed at the referred branches
MetricResults
ModuleResults
KalibroModules
Repositories
Processings
ProcessTimes
The text was updated successfully, but these errors were encountered:
First proposed by #215 and then isolated at the branch
db_indexes
(https://github.com/mezuro/kalibro_processor/tree/db_indexes).We've already seen that those indexes have some impact on insertion times adding 30s to the performance test on the worst case. We need now to investigate if there is real gain on other operations which are essentially reads (in contrast to the aggregation performance test which is biased to data insertion times).
The text was updated successfully, but these errors were encountered: