Bug #7302
closedBridge spends a lot of time for uploading a result of verification task
100%
Description
Bridge was uploading one result during one hour. May be the time is wasted while bridge is applying existed marks, so I also attached them.
Files
Updated by Evgeny Novikov almost 8 years ago
Perhaps this issue was already addressed in 3fbc468. I hope that this commit will find its way to master soon.
Updated by Vladimir Gratinskiy almost 8 years ago
- Due date set to 06/17/2016
- Status changed from New to Resolved
- % Done changed from 0 to 100
Optimized in branch "bridge-optimizations". Now it takes about 1.5 minutes. And only about 5-10 seconds is Bridge. Other time is graphml parser (which is python library I slightly changed for error traces support). I think we should think on another error traces format.
Upd. Opening error trace page also takes about 1.5 minutes due to the same reason.
Updated by Evgeny Novikov almost 8 years ago
- Status changed from Resolved to Closed
- Published in build set to 1127662
Updated by Evgeny Novikov almost 8 years ago
- Status changed from Closed to Open
Perhaps results are uploaded faster but the major bottleneck - the graphml parser - wasn't fixed. We noticed that the standard XML parser needs just a couple of seconds to read these error traces.
Updated by Evgeny Novikov over 7 years ago
- Priority changed from High to Immediate
This is yet another issue preventing useful marks.
Updated by Evgeny Novikov over 7 years ago
- Status changed from Open to Resolved
A new error traces format as well as its support in Bridge were implemented in branch better-unsafes-and-marks. No third party parsers are used any more, so I think that the bottleneck is gone.
Updated by Ilja Zakharov over 7 years ago
- Status changed from Resolved to Verified
Updated by Ilja Zakharov over 7 years ago
- Status changed from Verified to Closed