02 August 2011
Even when the geometry is almost empty, simulation runs too slow. Basic checks make it look like an effect of running RunManager->BeamOn(1)
Can we make a spill an event?
That's the solution I think, and a good thing to do anyway. It's a days work (means doing the EventAction properly).
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.
Do you think that Simon would mind setting up something like:
since the code is linked to at the bottom?
We can ask... (Simon added as watcher)
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.
- Status changed from Open to Closed
- % Done changed from 0 to 100
I think factor 2 is okay for now. Will close the issue.
- Target version changed from Future MAUS release to MAUS-v0.0.5
Also available in: Atom