Modify ↓
#33 closed enhancement (fixed)
Memory limit can be changed on the command line
Reported by: | bill.murray@stfc.ac.uk | Owned by: | support@sherpa-mc.de |
---|---|---|---|
Priority: | trivial | Milestone: | |
Component: | Unknown | Version: | 1.1.2 |
Keywords: | Cc: |
Description
Hello there,
I am running Sherpa 1.1.2 just now on a box with a dual core CPU and 4Gb
ram. Sherpa decides it can take 3.7Gb, but I have allocated 1GB to a virtual machine. It feels as if this is not being taken into account.
A minor problem, but maybe there is an easy solution? Bill
Attachments (0)
Change History (4)
comment:1 Changed 16 years ago by
Summary: | Memory detection too optimistic → Memory limit can be changed on the command line |
---|
comment:2 Changed 16 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 Changed 13 years ago by
Milestone: | → rel-old |
---|
Note: See
TracTickets for help on using
tickets.
Hi Bill,
you can start Sherpa with the commandline option "RLIMIT_AS = 2.7 GB". Be sure not to forget the quotes around everything and the space between number and unit. Otherwise the 'GB' option will not properly be recognized. Unfortunately there is no direct way to consider the memory assigned to another program, since we obtain the memory information directly from the system.
Best