Project

General

Profile

Bug #607

Simulation runs too slow

Added by Rogers, Chris about 10 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Simulation
Target version:
Start date:
02 August 2011
Due date:
% Done:

100%

Estimated time:
Workflow:

Description

Even when the geometry is almost empty, simulation runs too slow. Basic checks make it look like an effect of running RunManager->BeamOn(1)

#1

Updated by Tunnell, Christopher about 10 years ago

Without tracks?

Can we make a spill an event?

#2

Updated by Rogers, Chris about 10 years ago

That's the solution I think, and a good thing to do anyway. It's a days work (means doing the EventAction properly).

#3

Updated by Rogers, Chris about 10 years ago

I've implemented the event structure in my branch, a worthwhile thing to do anyway. Running now 100 events over just 3 RF cavities. Still get about factor 5 slowdown compared to G4MICE. Notice optimize flags aren't set, let's try that next.

#4

Updated by Tunnell, Christopher about 10 years ago

Do you think that Simon would mind setting up something like:

http://speed.pypy.org/

since the code is linked to at the bottom?

#5

Updated by Rogers, Chris about 10 years ago

We can ask... (Simon added as watcher)

ps:
Adding -O2 or -O3 gave factor 2 in speed, so still missing factor 2 somewhere. Doubt this is the persistency (getting 0.5 k data per primary), but don't know what else has changed. gprof next.

#6

Updated by Rogers, Chris about 10 years ago

  • Status changed from Open to Closed
  • % Done changed from 0 to 100

I think factor 2 is okay for now. Will close the issue.

#7

Updated by Rogers, Chris about 10 years ago

  • Target version changed from Future MAUS release to MAUS-v0.0.5

Also available in: Atom PDF