Message boards :
Sixtrack Application :
Memory requirement and VB vs. native
Message board moderation
| Author | Message |
|---|---|
|
Send message Joined: 14 Dec 11 Posts: 23 Credit: 101,345 RAC: 0  
|
I've been running Theory, since I currently only have 6 GB of memory. I have more on order, so that will soon be 12 GB. But I'm also interested in Sixtrack. How much memory is needed? A user who uses Linux directed me to a post from 2018 that says the Linux app itself uses ~7 MB, and Sixtrack tasks have a peak working set of ~350 MB each. I also don't know whether it's best to run Sixtrack natively or in a VM. |
|
Send message Joined: 18 Dec 15 Posts: 1847 Credit: 127,259,921 RAC: 136,006  
|
I also don't know whether it's best to run Sixtrack natively or in a VM.Sixtrack does NOT run in a VM (as opposed to Atlas and Theory). |
 Veronica Send message Joined: 29 Sep 17 Posts: 14 Credit: 5,244,196 RAC: 0 |
Exactly how much is allocated depends mostly on what accelerator description is being simulated, but also on how many particles is being tracked. The latter is usually a small number for BOINC jobs. ~300MB seems about right for SixTrack 4. SixTrack 5 generally uses less memory than older versions as memory is allocated as needed as opposed to fixed allocations in SixTrack 4. SixTrackTest should therefore in general use less memory than the production version. We will soon switch production to running on SixTrack 5. SixTrack 5 Core Developer. github.com/SixTrack/SixTrack |
|
Send message Joined: 14 Dec 11 Posts: 23 Credit: 101,345 RAC: 0
|
Thanks Veronica. I now have 12 GB of memory, so I think I could run Atlas tasks again when it comes back online. So does the sixtracktest application run the developer versions? |
|
Veronica Send message Joined: 29 Sep 17 Posts: 14 Credit: 5,244,196 RAC: 0 |
Thanks Veronica. I now have 12 GB of memory, so I think I could run Atlas tasks again when it comes back online. So does the sixtracktest application run the developer versions? SixTrack is under continuous development as new features are added regularly due to specific needs for studies being performed by the various groups at CERN that uses SixTrack. We therefore do frequent patch releases with new features on our main repository, as well as fixes and other tweaks. A lot of these releases are not intended for BOINC use, so we do specific BOINC releases whenever we need to put new features into the SixTrackTest queue. They are not developer versions per say, but when we have a version that performs well on SixTrackTest, we intend to bump it to the main queue. SixTrack 5 Core Developer. github.com/SixTrack/SixTrack |
©2025 CERN