Project

General

Profile

Actions
Copy link

Bug #2992

open

Cl2d runs in garibaldi taking much longer than in guppy to upload

Added by Yong Zi Tan about 10 years ago. Updated about 10 years ago.

Status:
New
Priority:
Normal
Assignee:
Sargis Dallakyan
Category:
-
Target version:
-
Start date:
12/10/2014
Due date:
% Done:

0%

Estimated time:
Affected Version:
Appion/Leginon 3.1.0
Show in known bugs:
No
Workaround:

Description

I have noticed that my garibaldi cl2d runs take much longer to complete than corresponding runs in the guppy server. As example, the following two runs were for the same stack with the same parameters:

Garibaldi Run using 64 processors (/ami/data15/appion/14nov19f/align/cl2d6/)
8 days 23 hr
  • Proc2d took 17 hr 38 min
  • Alignment took 2 days 13 hr
  • Uploading took rest of the time
Guppy Run using 8 processors (/ami/data15/appion/14nov19f/align/cl2d7/)
3 days 21 hr
  • Proc2d took 1 hr 26 min
  • Alignment took 2 days 23 hr
  • Uploading took rest of the time
Actions
Copy link
 #1

Updated by Sargis Dallakyan about 10 years ago

Thank you Yong. This is seems to be issue with networking and how many network switches the signal needs to hop to reach to the database server. It would be interesting to see what these numbers would look like when the new database server is installed near garibaldi.

Actions
Copy link

Also available in: Atom PDF