Of the 13 processors of the VPP300, only the primary processing
element can be logged in to for ordinary interactive use. The primary PE is called PE0 or vpp00 by the system, and can be accessed on the internet via vpp.anu.edu.au. See the
System Overview for detail of the
role of the primary PE vs the Secondary PEs.
Limits on Interactive Use
Each interactive process you run has imposed on it a time limit and a
memory use limit. To see what these limits are enter the command
anu_limits. This shows not only the details of the memory
limits and time limits for interactive processes, but for batch jobs
as well. The limits are not published here as they are liable to
change.
If your process exceeds the memory limit, the simple message
"Killed" will be returned to you by the Unix operating system. If
your process does not exceed the limit, but does exceed the current
physical amount of memory available, you might get something a little
more informative, like "Not enough space". Beware, such a message
will also appear if you have filled your disk quota on your home
directory, and your process is trying to open a new file to write to.
Refer to the System Overview to see
how memory on PE0 is divided between batch jobs, interactive vector
jobs, and scalar jobs. Also note the relative lack of scalar memory on
the secondary PEs, and the importance of NOT running scalar batch jobs.
Commands to find current "status".
- anu_limits will display imposed limits and charging rates.
- quotasu -P project will display the usage of the project in
the current quarter
- quota -v will display your disk usage and quota in your home
directory.
- nqstat -c = -l to display status of all running and queued batch jobs.