[#PIPE2D-208] Redo the profiling on a larger fraction of the code

[PIPE2D-208] Redo the profiling on a larger fraction of the code Created: 23/Jun/17 Updated: 03/Nov/18 Resolved: 03/Nov/18
Status:	Done
Project:	DRP 2-D Pipeline
Component/s:	None
Affects Version/s:	None
Fix Version/s:	None

Type:

Story

Priority:

Major

Reporter:

rhl

Assignee:

Unassigned

Resolution:

Done

Votes:

Labels:

None

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Description

Paul took a first pass at the profiling in ~~PIPE2D-127~~, but I think we need to repeat the work with multiprocessing turned off (--batch-type None) and hope/pray that some of the hot spots have been eliminated.

Also, we should profile the full runPipeline script.

If appropriate, this ticket should file tickets to fix hot-spots (some are indicated in ~~PIPE2D-127~~).

Comments

Comment by hassan [ 03/Nov/18 ]

Will raise a separate ticket once the end-to-end (SIM2D + 2D DRP) pipeline is running and the speed performance is understood.

Generated at Sat Feb 10 15:49:34 JST 2024 using Jira 8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b.

[PIPE2D-208] Redo the profiling on a larger fraction of the code Created: 23/Jun/17 Updated: 03/Nov/18 Resolved: 03/Nov/18