Project

General

Profile

Bug #5297

Workflow Run Manager - no indication of progress during preview runs download

Added by Derik Barseghian almost 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Normal
Category:
workflow run manager
Target version:
Start date:
02/07/2011
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5297

Description

There are currently about 131 run-kars on kepler-dev. Switching to kepler-dev from the workflow run manager for the first time takes (including authentication), upwards of 30s for me, and I'm on a fast university connection. A busy icon shows during the wait, but it would be better if each preview run showed up in the WRM as it was downloaded, instead of waiting until all are downloaded.
Also look into speeding up this process, e.g. check with Jing about caching the search results on metacat, look for bottlenecks (disk i/o with the tracker xml file?), etc.

History

#1 Updated by Matt Jones almost 9 years ago

Derik,

When we discussed this before, I think we concluded that the search time was largely due to Kepler issuing an EcoGrid get() request for every result record, which obviously doesn't scale. The Metacat search itself should be subsecond for up to thousands of records. Metacat needs to be configured properly for that to work though -- in that the karxml fields need to be indexed for search to be fast. Other than that, its probably a client-side issue in its decision to download all of the KARs.

#2 Updated by Derik Barseghian almost 9 years ago

This bug is just for fetching data needed to build "preview" WorkflowRuns (bits from the karXML, not the kars or entire karXMLs). I get all records in one query to metacat. I did some quick timing tests of WRM with kepler-dev (there are a few reasons why these shouldn't be considered exact, but they give a good rough idea) :

The ~30s that it currently takes to show all ~131 preview runs for a first time switch of WRM to kepler-dev breaks down roughly:
1) "anon" authentication via kepler gui: ~6s
2) query to fetch all data needed to build workflowRuns: ~4s
3) locally building runs, writing to provenance and tracker file: ~17s

For a subsequent Refresh action:
1) ~0s (already authenticated)
2) ~3s
3) ~0s

So I'll look into improving #3, the big cost must be the write actions.

#3 Updated by Derik Barseghian almost 9 years ago

"fixed" at r27053.
Step #3 now takes about 2s instead of 17.
Refactoring to show the preview runs as they're imported would take a fair bit of work, especially to avoid putting us right back at 17s+, and at 2s wait it's not worth it.

#4 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 5297

Also available in: Atom PDF