Actions
Feature #7350
closedOptimize association of marks with safe reports
Start date:
06/28/2016
Due date:
09/12/2016
% Done:
10%
Estimated time:
Published in build:
Description
Now it is performed abnormally long although it seems that no large computations, e.g. error trace comparison, should be actually done.
Updated by Evgeny Novikov over 8 years ago
- Priority changed from Normal to Immediate
This is yet another issue preventing useful marks.
Updated by Vladimir Gratinskiy over 8 years ago
- Due date set to 09/12/2016
- Status changed from New to Feedback
- % Done changed from 0 to 10
The only thing I can do is optimize creation of connections. Searching of attributes of all marks/safes is too long and can't be optimized because of our DB structure. To fix it we should do something with attributes. Small optimizations are done in branch "feature_7350".
Updated by Evgeny Novikov over 8 years ago
I tried to test this but I couldn't do that since safe marks can't be created.
Updated by Evgeny Novikov over 8 years ago
- Status changed from Feedback to Closed
I merged this branch to master in df659a3. Safe marks are created much more faster now.
Actions