whizard is hosted by Hepforge, IPPP Durham

Opened 14 years ago

Closed 8 years ago

#415 closed task (fixed)

Resurrect the MPI version of VAMP

Reported by: kilian Owned by: brass
Priority: P1 Milestone: v2.6.0
Component: vamp Version: 2.0.5
Severity: major Keywords:
Cc:

Description

Regarding VAMP, this is probably fully functional already, but some work may have to be done on the WHIZARD side.

This would nicely complement the OpenMP implementation in the innermost loop (the sampling function).

Change History (12)

comment:1 Changed 13 years ago by Juergen Reuter

BTW, is there any update on this?

comment:2 Changed 13 years ago by kilian

Update from MT: the MPI version is complete and compiles, but VAMP(I) doesn't produce correct numbers yet. Debugging.

comment:3 Changed 13 years ago by Juergen Reuter

Milestone: v2.1.1v2.1.0

After reports from Siegen, this might hopefully be ready earlier....

comment:4 Changed 13 years ago by Juergen Reuter

Milestone: v2.1.0v2.2.0

comment:5 Changed 9 years ago by Juergen Reuter

Owner: changed from trudewind, ohl to brass

Guess this job moved now to SB.

comment:6 Changed 8 years ago by Juergen Reuter

Milestone: v2.3.0v2.4.0

comment:7 Changed 8 years ago by Juergen Reuter

Milestone: v2.4.0v2.5.0

Milestone renamed

comment:8 Changed 8 years ago by kilian

Priority: P3P1

The actual re-implementation has been done by SB.

Now, the code has to be merged with the master branch, but there are some open questions about the top-level management of the MPI workers in the context of the WHIZARD workflow. Profiling would also be useful.

There is significant and linear speedup, even for 100 cores, provided the number of calls for channel is sufficiently large.

For parameter sets with a small number of calls per channel, there is saturation. A possible solution is indicated in ticket #818

comment:9 Changed 8 years ago by Juergen Reuter

Milestone: v2.5.0v2.6.0

Milestone renamed

comment:10 Changed 8 years ago by Juergen Reuter

This has been merged (fully) with the master. Documentation is under way, but still pending and not yet in the master. Benchmarking is also in the making. Shall we close the ticket, as there are already more specialised tickets like #818?

comment:11 Changed 8 years ago by Juergen Reuter

Component: corevamp

comment:12 Changed 8 years ago by Juergen Reuter

Resolution: fixed
Status: newclosed

After discussion with SB, this ticket will be happily closed. All technical improvements and benchmarking as well as documentation will be part of specialized tickets.

Note: See TracTickets for help on using tickets.