Project

General

Profile

Actions

Bug #7302

closed

Bridge spends a lot of time for uploading a result of verification task

Added by Pavel Andrianov over 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Immediate
Category:
Bridge
Target version:
-
Start date:
06/17/2016
Due date:
06/17/2016
% Done:

100%

Estimated time:
Detected in build:
svn
Platform:
Published in build:
1127662

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

Marks--17-6-2016.tar.gz (36.4 KB) Marks--17-6-2016.tar.gz Pavel Andrianov, 06/17/2016 03:17 PM
unsafe1 report.json (392 Bytes) unsafe1 report.json Pavel Andrianov, 06/17/2016 03:23 PM
unsafe1 report files.tar.gz (296 KB) unsafe1 report files.tar.gz Pavel Andrianov, 06/17/2016 03:23 PM

Related issues 1 (0 open1 closed)

Related to Klever - Bug #7400: Klever takes too much time to upload reportsRejectedVladimir Gratinskiy07/14/2016

Actions
Actions #1

Updated by Evgeny Novikov over 8 years ago

Perhaps this issue was already addressed in 3fbc468. I hope that this commit will find its way to master soon.

Actions #2

Updated by Vladimir Gratinskiy over 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.

Actions #3

Updated by Evgeny Novikov over 8 years ago

  • Status changed from Resolved to Closed
  • Published in build set to 1127662

The branch was merged to master in 1127662. Please, see #6710 for details.

Actions #4

Updated by Evgeny Novikov over 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.

Actions #5

Updated by Evgeny Novikov over 8 years ago

  • Priority changed from High to Immediate

This is yet another issue preventing useful marks.

Actions #6

Updated by Evgeny Novikov over 8 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.

Actions #7

Updated by Ilja Zakharov about 8 years ago

  • Status changed from Resolved to Verified
Actions #8

Updated by Ilja Zakharov about 8 years ago

Merged in 6e2305dc.

Actions #9

Updated by Ilja Zakharov about 8 years ago

  • Status changed from Verified to Closed
Actions

Also available in: Atom PDF