PSC Blacklight User Guide
Blacklight is an SGI UV 1000cc-NUMA shared-memory system comprising 256 blades. Each blade holds 2 Intel Xeon X7560 (Nehalem) eight-core processors, for a total of 4096 cores across the whole machine. Each core has a clock rate of 2.27 GHz, supports two hardware threads and can perform 9 Gflops. The sixteen cores on each blade share 128 Gbytes of local memory. Users can run shared memory jobs of up to 16 Tbytes.
Blacklight runs an enhanced version of the SuSE Linux operating system.
Blacklight also has frontend processors. You login to one of these frontend processors, not to Blacklight's compute processors. You will usually prepare your job files and compile your programs on one of these front ends, but you should not run your programs on the frontends because they have limited resources. You should instead run your programs using Blacklight's batch system. Thus, frontend computations will be killed if they consume too much processor computational time or processor memory. A message will be sent to your display indicating how you violated these resource limits if you run one of these offending computations. How to run a job on Blacklight's compute processors with the
qsub command is discussed below.
The Intel C, C++ and Fortran compilers and the Gnu Fortran, C and C++ compilers are installed on Blacklight, as are the facilities to enable you to run threaded, MPI and hybrid threaded and MPI programs. OpenMP programs are a common type of threaded programs that are supported on Blacklight. UPC and Java are available on the machine and are briefly documented below. In the future, more programming models which exploit the unique architectural features of Blacklight will be available. When those models are available their use will be described in this document.
Also available are an array of performance tools, debuggers and libraries. A complete list of packages installed on Blacklight is available online.
File systems are file storage spaces directly connected to a system. There are currently three such areas available to you on Blacklight.
This is your home directory. Your
$HOMEdirectory has a 5-Gbyte quota.
$HOMEis visible to all of Blacklight's compute and frontend processors.
$HOMEis backed up daily, although it is still a good idea to store your important
$HOMEfiles to the Data Supercell. The Data Supercell, PSC's file archival system, is discussed below.
You can check your home directory space usage using the command:
$ cd; du -sh
This is Blacklight's scratch area to be used as a working space for your running jobs.
$SCRATCHis visible to all of Blacklight's compute and frontend processors.
$SCRATCHis a parallel file system. The current capacity of
$SCRATCHis 291 Tbytes.
$SCRATCHis not a permanent storage space. Files can only remain on
$SCRATCHfor up to 21 days and then we will delete them. In addition, we will delete
$SCRATCHfiles if we need to free up space to keep jobs running. Finally,
$SCRATCHis not backed up. For these three reasons, you should store copies of your
$SCRATCHfiles to your local site or to the Data Supercell as soon as you can after you create them. The Data Supercell, PSC's file archival system, is discussed below. For information on improving your
$SCRATCHIO performance see the section on IO optimization below.
You should use
$SCRATCHas your scratch area. You should not use
/tmpfor this purpose. You should never need to write data to
You can check your scratch directory space usage by using the command:
$ cd $SCRATCH; du -sh
XWFS is a wide area file system mounted on Blacklight. It is also mounted on all major XSEDE computational machines to facilitate seamless file sharing between XSEDE systems.
You apply for an XWFS allocation through the XSEDE Portal. When you apply for an XSEDE allocation you specify a space quota, a list of users and a project name. The project name determines the name of your XWFS project directory under the directory /xwfs/projects, which is mounted on all major XSEDE computational platforms. Your XWFS quota is a group quota. The group includes all the users you listed in your XWFS allocation. Eventually the PI will be able to see the group's usage through the XSEDE Portal. For now you can use local Unix commands like du -sh.
You can use Unix commands, such as ls or cp, to manipulate your XWFS files on XSEDE systems. Any files you locally create and store into the XWFS file system will be available on other XSEDE machines. The XWFS file system is only mounted on frontend nodes, not on compute nodes, for performance reasons. Any file transfer commands you can use with your other files can be used with XWFS files.
File repositories are discrete file storage spaces. You will not, for example, open a file that resides in a file repository nor will you run a program on a file repository. You will not login to a file repository. You currently have one file repository available to you on Blacklight: the Data Supercell, PSC's file archival system.
Blacklight is a machine with a very large shared memory and many cores. Thus, if your application needs large shared memory, Blacklight may be a suitable platform for you, whether your job needs a few dozen cores or thousands of cores. Blacklight also has a large set of installed software packages that exploit Blacklight's unique hardware features. If you need a package that is not installed, send email to email@example.com to ask PSC to consider the installation of that package.
XSEDE provides a set of tools and services to help you to decide if Blacklight or any other XSEDE supercomputer is appropriate for your work. XSEDE provides a catalog of available XSEDE resources and their features. XSEDE also provides a list of available science gateways. Gateways are specialized interfaces that can make your work easier. Finally, XSEDE provides a list of Campus Champions. A Campus Champion is a local contact you can use to discuss whether a supercomputer would be useful for your work.
Test runs on your local systems can be used to determine if a supercomputer is necessary for your research. You can also send email to firstname.lastname@example.org for consulting assistance to help you determine whether a supercompter would be helpful to you.
Once you decide you would like to use an XSEDE resource, such as Blacklight, you must apply for an allocation through the XSEDE User Portal. The first step in using the Portal is to apply for a Portal account. Then you can determine if you are eligible to become a Principal Investigator for an XSEDE allocation. Normally your first XSEDE proposal will be for a Startup allocation, but you can also apply directly for a Research allocation. If you are applying for a Startup allocation do not spend a lot of time estimating your SU usage. One of the purposes of a Startup allocation is to make such estimates. A complete description of the allocation policies for applying for allocations for using XSEDE resources is available online.
PSC's Blacklight compute resource allocations are managed by the XSEDE program, which is supported by the National Science Foundation. For more information on applying for an allocation on Blacklight see the instructions at https://www.xsede.org/web/guest/new-allocation.
Once you have a Blacklight account, there are several scenarios that can disrupt your project's progess. First, you can experience difficulties getting started. Running on a supercomputer is not a frictionless task. If you find yourself in this position, send email to email@example.com. PSC has several levels of consultants available to help you. This assistance ranges from basic questions of computer usage to scientific support for your particular project. PSC consultants will be able to assist you in getting your project started. XSEDE has also developed online resources to help you with your initiation into supercomputing and Unix. Finally, searching for "introduction to supercomputing" or "introduction to Unix" on the Web will yield a number of useful sites.
A second issue that can derail your project is running out of SUs. A Service Unit (SU) is defined as the use of one core for one hour. When you receive an allocation, you are awarded an amount of computing time on a resource defined in terms of SUs. Each allocation also has an expiration date. To prevent the situation of running out of SUs from occurring, so that you can continue to compute without interruption, you should frequently monitor your SU balance with the Blacklight xbanner command. If you are running out of SUs you have several options. If your allocation does not expire for at least three months, you can submit a Renewal proposal for the next XRAC meeting and then ask for up to 25% of your SUs in your new award as an advance. If your allocation expires in less than three months you can request a Supplement to your current allocation. A third option is to transfer SUs from another machine on your allocation to Blacklight.
These actions of submitting a Renewal request, asking for an advance, asking for a Supplement or transferring SUs must all be done by the allocation's PI through the XSEDE POPS system. This system must be accessed through the XSEDE User Portal account. Detailed descriptions for these operations with your SUs are available online.
Another event that can interrupt your computing is the expiration of your allocation. Even though you have distinct PSC and XSEDE Portal userids they are linked as far as expiration is concerned. When one expires the other will expire. To insure that you are not caught unawares by an allocation expiration you should continually monitor your expiration dates with the Blacklight xbanner command. The XRAC committee meets every three months. Thus, when your allocation approaches three months from expiration the PI for the allocation should submit a Renewal request to XRAC. If you have an expiring Startup allocation the PI should almost always submit a Research proposal to XRAC. Renewals of Startup allocations are rarely given. The data you gathered from using your Startup allocation can be used as justification in your Research proposal.
If your allocation is going to expire and you estimate that you will have SUs left when it does, you can respond differently. For example, you obtained a Startup allocation, but did not use it very much. In this situation, instead of submitting a proposal for a new allocation, you can apply for an Extension of up to six months for your existing allocation.
These actions of submitting a Renewal request, submitting a Research proposal or asking for an allocation Extension must all be done by the allocation's PI through the XSEDE POPS system. This system must be accessed through the XSEDE User Portal account. Detailed descriptions of the policies for these operations are available online.
A fourth impediment to the progress of your project is the need to add a user to an allocation. The PI for the allocation must add all users to an allocation by using the Add User form, which must be accessed through the PI's XUP account. Each user to be added must have already created, by using the User Portal, a User Portal userid. The policies for adding a user are described online
There are three methods you can use to connect to Blacklight.
You can connect to Blacklight by using XSEDE's single-signon process, either through the XSEDE Portal or by downloading the necessary software components to your local machine. There is also a single-signon hub you can use if you want a command-line interface, but still want to have single-signon access to your XSEDE resources. These methods are especially useful if you have allocations on more than one XSEDE resource. To use these methods you must have an XSEDE allocation. To connect through the Portal you use your XSEDE Portal userid and password.
You can also connect to Blacklight by using
ssh to connect to blacklight.psc.xsede.org. When you are prompted for a password by
ssh enter your PSC Kerberos password. Your PSC Kerberos password is not the same as your XSEDE Portal password nor is your PSC userid necessarily the same as your XSEDE Portal userid. You will need to set your PSC Kerberos password before the first time you connect to Blacklight using
ssh. This method can be used with any type of Blacklight allocation.
Finally, you can connect to Blacklight using a public-private key pair. The procedure to do this is available online. You will need to set your PSC Kerberos password before you can use this procedure. This method can be used with any type of Blacklight allocation.
If you have problems connecting to Blacklight, either when you first get your account or after you have had your account for a while, send email to firstname.lastname@example.org.
Your PSC Kerberos password is not the same as your XSEDE Portal password. Resetting one password does not change the value of the other password. You use your PSC password to connect to Blacklight and other PSC machines with
ssh. You use your XSEDE password when you connect using the XSEDE Portal.
There are two ways to change or reset your PSC Kerberos password:
- Use the web-based PSC password change utility
- Use the
kpasswdcommand to change your PSC Kerberos password. Do not use the
You have the same password on all PSC production platforms. When you change your password, whether you do it via the online utility or via the
kpasswd command on one PSC system, you change it on all PSC systems.
PSC Kerberos passwords must be at least 8 characters in length. They must also contain characters from at least 3 of the character classes:
- lower-case letters
- upper-case letters
- special characters, excluding ' and "
Finally, they must not be the same as any of your previous passwords.
You must change your Blacklight password within 30 days of the date on your initial password form or your password will be disabled. We will also disable your password if you do not change it at least once a year. We will send you an email notice warning you that your password is about to be disabled in the latter case. See the PSC password policies for more information.
If you have a password issue and communicate with PSC about this problem through remarks do not include your password in an email messasge.
You can use the
chsh command to change your login shell. When doing so, specify a shell from the /usr/psc/shells directory.
One core-hour on Blacklight is one SU. Because resources are allocated by blades and not by cores--jobs do not share blades--your SU charges will always be based on core usage that is a multiple of sixteen. A one blade job that runs for one hour costs 16 SUs.
If you have more than one account, use the
qsub option "
-W group_list" to indicate to which account you want a job to be charged. The use of this option is discussed in the "Other
qsub options" subsection of this document. To change your default account you must send email to email@example.com with this request.
There are several tools you can use to track your account usage data. User accounting data is available with the xbanner command. Account information including the initial SU allocation for an allocation, the number of unused SUs remaining for an allocation and the date of the last job that charged to an allocation are displayed.
Accounting information is available at the Web-based PSC Grant Management System. You will need your PSC Kerberos password to access this system. This system provides more detailed information than xbanner, although some of the information is only available to PIs, co-PIS and individuals designated by the PI to see accounting data. The system has extensive internal documentation.
You can use the xdusage command on Blacklight to see your Blacklight accounting data. You can also use the "
-r" option to xdusage to check your accounting data on other XSEDE resources. A man page is available for xdusage as well as online documentation.
Finally, the Portal login dashboard displays your accounting data for all your XSEDE resources.
A variety of transfer methods are available to copy files to and from Blacklight's file systems.
Since your Blacklight home directory has a limited amount of space, you will not be able to transfer much data into your home directory. Exceeding your home directory quota will prevent you from writing more data to your home directory, and will adversely impact other operations you might want to perform. Instead, you should transfer your files to the Data Supercell. Then, when you need your files on Blacklight you can transfer them to your Blacklight scratch area. Your scratch area is not a permanent storage space. Thus, you must manage the transfer of your files between
$SCRATCH and the Data Supercell so that files you want to retain are not deleted by the 21-day wiper. Nor are your scratch files backed up, which is an additional motivation for you to move your files to the Data Supercell or to your local storage in a timely manner.
You can also copy files directly into your scratch area, although you must be aware of the 21-day wiper and of the fact that scratch files are not backed up when storing files in this area. The discussion of file transfer methods below will describe how to copy files directly into
$SCRATCH. You should consult the Data Supercell user guide for information on copying files into the Data Supercell.
Our recommend method for file transfer into Blacklight is Globus, both between your local file system and Blacklight and between Blacklight and the Data Supercell. To be able to use Globus you must obtain proper credentials, either from XSEDE or InCommon. If you cannot use Globus, but do have access to Globus client software, our next recommended method is to
globus-url-copy. Otherwise, you should use either the
tar method discussed below or
scp. You should the former methods if you are transferring a lot of small files.
PSC maintains a Web page that lists average data transfer rates between all XSEDE resources, including Blacklight and the Data Supercell. For example, you can find the average data tranfer rate between Blacklight and the Data Supercell in this table. If your transfer rates are significantly lower than these average rates or you believe that your file transfer performance is subpar, send email to firstname.lastname@example.org. We will examine approaches for improving your file transfer performance.
Globus is our recommended method of transferring data to and from the Data Supercell. To use Globus you must first create a Globus userid and password at the Globus Web site. Once you have logged in to Globus you can initiate your file transfer. For each file transfer you must select two Globus endpoints, to which you must then authenticate. The endpoint to use for Blacklight is
xsede#pscdata. If you are an XSEDE user you can use your XSEDE Portal userid and password to authenticate to the Globus endpoint
xsede#pscdata. When connecting to the
xsede#pscdata endpoint on Globus you may be redirected to the XSEDE OAuth page to enter your XSEDE Portal username and password for authentication. After authentication, you will automatically be returned to the Globus site to initiate your transfers.
If you are affiliated with an InCommon institution you can use your userid and password for that institution to authenticate to endpoint
psc#dsc-cilogon if you have previosuly registered with PSC as an InCommon user. To register with PSC as an InCommon user you must follow the steps below. You only need to follow these steps once.
- Point your browser to https://cilogon.org/, select your institution from the 'Select and Identity Provider' list, and click on the 'Log On' button. This should take you automatically to a login page for your institution.
- Enter your username and password for your institution on the login page, and click on the 'Login' button. You should then get redirected back to the CILogon Service webpage.
- In a box near the top of the CILogon Service webpage there should appear a field called "Certificate Subject" with a string like/DC=org/DC=cilogon/C=US/O=My Institution/CN=My Name A1234Copy this string to a clipboard or text file. You'll need to paste it into a field on another webpage shortly.
- Log Off from the CILogon Service webpage.
- Point your browser tohttps://dirs.psc.edu/cgi-bin/teragrid/userpage/list.pland login with your PSC userid and password. This site lists the certificate subjects (DNs) that we have in our PSC database for your PSC account. You will be adding the CILogon certificate subject (DN) to this list.
- Click on the 'Add DN' link at the top left. This should get you to the "Adding DN" page, where you paste into the DN: field the certificate subject that you copied in step 3 above. Make sure there are no extra spaces before or after the pasted string. Click on 'Create' to add your new CILogon DN (certificate subject) to the PSC database.
- Click on the 'List DNs' link at the top left to confirm that your new DN was added.
Within an hour you should be able to use Globus by authenticating to the
psc#dsc-cilogon endpoint using your userid and password at your institution. You should only need to perform this authentication once per Globus session or for as long as the retrieved credentials are valid. Send an email to email@example.com if you have any questions about using InCommon.
If you are unable to use either the XSEDE or InCommon methods of authentication to Globus send email to firstname.lastname@example.org to see if you can use other methods of authentication to Globus.
If you do not enter a path for the endpoints
psc#dsc-cilogon your destination will be your Data Supercell home directory. Thus, you must explicitly enter the path to your Blacklight scratch directory to make it the target of your file transfer. We do not recommend transferring large files into your Blacklight home directory, because your home directory space is limited. To use Globus to transfer files into your home directory you must enter the path to your home directory.
You can also use Globus to transfer files between your Blacklight scratch space and the Data Supercell. In fact, Globus is our recommended method for performing this type of transfer. To perform this transfer you would use
xsede#pscdata for both endpoints, since
xsede#pscdata can also be used to point to Blacklight. To make your second endpoint point to your brashear files you must enter as your Globus path for this endpoint the complete path to your brashear directory. Otherwise, Globus will use your Data Supercell home directory as your path in the transfer.
For example, suppose you want to transfer brashear file largematrix.dat to your Data Supercell home directory. You would enter
xsede#pscdata for both endpoints. For the path for the endpoint you are using to point to Blacklight you must enter your path as "
/brashear/joeuser/largematrix.dat". For the other path, the path pointing to the Data Supercell, you can enter just largematrix.dat, since you are storing the file in your home directory on the Data Supercell. Then you can initiate the transfer by clicking the appropriate arrow button.
The tar command, in conjunction with the
ssh command, can also be used to transfer files to Blacklight. This approach is especially useful if you are transferring a lot of small files.
There are two methods of using tar. In both methods you use tar as part of your transfer command. The first method enables you to have a tarball on Blacklight without having to create one on your source system. If you create a tarball on your source machine before you transfer it to Blacklight you double your storage usage on your source system. The first method of using tar in your transfer command avoids this doubling of space usage. A sample command is:
$ tar cf - sourcedir/ | ssh blacklight.psc.xsede.org "cat > /brashear/joeuser/bldir.tar"
For 'sourcedir' you substitute the name of your source directory and for 'joeuser' you substitute the name of your PSC userid. The result of this command will be the tarball bldir.tar on Blacklight without the need to first create it on your source system. You can run the process in reverse when you copy files from Blacklight back to your source system.
In the second method the result is not a tarball, but the same set of individual files you have on your source system. A sample command is:
$ tar -cf sourcedir/ | ssh blacklight.psc.xsede.org tar xf - -C /brashear/joeuser
For 'sourcedir' you substitute the name of your source directory and for 'joeuser' you substitute your PSC userid. The result will be the same as the equivalent
scp command, but the transfer will be faster. You should use the first method of using tar if you have a lot of individual files, because your performance will deteriorate if you transfer a lot of individual files.
If you are not concerned about your local disk storage or the performance of
scp or want to use a simpler method, you can use tar on your local system and then use
scp to transfer your file to the Data Supercell and from there to your Blacklight scratch area.
A sample set of commands on your local machine would be
$ tar cf sourcedir.tar sourcedir
$ scp sourcedir.tar email@example.com
You can compress your tarball before you transfer it to speed up your transfer times. Then you could login to Blacklight and issue the commands:
$ cd $SCRATCH $ tar xf /arc/users/joeuser/sourcedir.tar
This will unroll your tar file in your scratch directory.
You can use the SSH file transfer clients
scp to transfer files between your local systems and Blacklight filesystems. When using
scp to transfer files to and from Blacklight you do not connect directly to Blacklight.You transfer files using a PSC high-speed data conduit named data.psc.xsede.org. You transfer files to and from Blacklight via data.psc.xsede.org. If you are not connected to the data conduit from an XSEDE host you must use the name data.psc.edu for the data conduit. If you have a graphical
scp client application on your local system, you can use it to connect and authenticate to data.psc.xsede.org or data.psc.edu and transfer files accordingly. Use your PSC userid and password for authentication.
If you need to (re)set your PSC password, you can do so via the
kpasswd command on any PSC production system, or using the http://apr.psc.edu/Web form.
You can use the command-line
sftp client to transfer files to and from Blacklight interactively. When using
sftp from the command line, you first connect and authenticate to data.psc.xsede.org, and then issue commands at the
sftp> prompt to transfer and manage files:
$ sftp firstname.lastname@example.org
joeuser is your PSC userid. The first time you connect to data.psc.xsede.org using
scp, you may be prompted to accept the server's host key. Enter
yes to accept the host key:
The authenticity of host 'data.psc.xsede.org (188.8.131.52)' can't be established. RSA key fingerprint is d5:77:f2:d9:07:f6:32:b6:c3:eb:0d:d1:29:ed:9b:80. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'data.psc.xsede.org' (RSA) to the list of known hosts.
You will then be prompted to enter your PSC password:
email@example.com's password: Connected to data.psc.xsede.org. sftp>
sftp> prompt, you can then enter
sftp commands (e.g.,
get, etc.) to manage and transfer your files to/from Blacklight. Enter a question mark (
?) for a list of available
Your default directory when using data.psc.xsede.org is your Data Supercell home directory. To access your Blacklight scratch directory you must change your directory to be your Blacklight scratch directory or use your entire scratch directory path in your
sftp command. Your scratch directory path will be similar to "
/brashear/joeuser". To access your Blacklight home directory you must change your directory to be your Blacklight home directory or use your entire home directory path in your
sftp command. Your home directory path will be similar to "
joeuser is your PSC userid, and entered commands appear in
Where am I (on the data.psc.xsede.org server)?
sftp> pwd Remote working directory: /arc/users/joeuser
Change directories to my Blacklight
sftp> cd /brashear/joeuser Remote working directory: /brashear/joeuser
Where am I on my local system?
sftp> lpwd Local working directory: /Users/JoeUser/Documents
Change directories on my local system to
sftp> lcd /usr/local/projects/example/data
Make a new directory called "
newdata" under my Blacklight
sftp> mkdir /brashear/joeuser/newdata
Copy a file (
file1.dat) from my current local directory to my Blacklight
sftp> put file1.dat /brashear/joeuser/newdata/file1.dat Uploading file1.dat to /brashear/joeuser/newdata/file1.dat file1.dat 100% 1016KB 1.0MB/s 00:00
Copy a file from my Blacklight
/usr/local/projects/example/data/newfile1on my local system :
sftp> get /usr/users/0/joeuser/file1 /usr/local/projects/example/data/newfile1 Fetching /usr/users/0/joeuser/file1 to /usr/local/projects/example/data/newfile1 /usr/users/0/joeuser/file1 100% 31 0.0KB/s 00:00
Exit from this sftp session :
For scripted transfers, or transfers that you want to execute directly from your command-line shell, you can use the SSH
joeuser is your PSC userid, and entered commands appear in
**bold**, and you enter your PSC password when prompted):
Copy my local file (
/usr/local/projects/example/data/file1.dat) to my Blacklight
$ scp /usr/local/projects/example/data/file1.dat firstname.lastname@example.org:/brashear/joeuser email@example.com's password: file1.dat 100% 1016KB 1.0MB/s 00:00
Copy the contents of my Blacklight
/usr/local/projectson my local system (creating
/user/local/projects/newdataand copying all the files there):
$ scp -r firstname.lastname@example.org:/brashear/joeuser/newdata /usr/local/projects email@example.com's password: file2.dat 100% 1016KB 1.0MB/s 00:00 file3.dat 100% 1016KB 1.0MB/s 00:01 file1.dat 100% 1016KB 1.0MB/s 00:00
XSEDE users may use GridFTP to transfer files to and from Blacklight filesystems.
To use the command-line
globus-url-copy client on a Blacklight login node, first ensure that you have a current user proxy certificate for authentication with enough time on it to complete your transfer, e.g.:
joeuser@tg-login1:~> grid-proxy-info subject : /C=US/O=National Center for Supercomputing Applications/CN=Joe User issuer : /C=US/O=National Center for Supercomputing Applications/OU=Certificate Authorities/CN=MyProxy identity : /C=US/O=National Center for Supercomputing Applications/CN=Joe User type : end entity credential strength : 2048 bits path : /tmp/x509up_u99999 timeleft : 11:58:33
If the timeleft is not sufficient, or you get an "
ERROR: Couldn't find a valid proxy" message, then use myproxy-logon (or if you have your own long term user certificate, grid-proxy-init) to obtain a new user proxy certificate, e.g.:
joeuser@tg-login1:~> myproxy-logon -l joexsedeuser -t 24 Enter MyProxy pass phrase: A credential has been received for user joexsedeuser in /tmp/x509up_u99999.
joexsedeuser is your XSEDE User Portal login name, "
-t 24" requests a 24-hour certificate, and the
MyProxy pass phrase entered is your XSEDE User Portal password.
You can then use
globus-url-copy to transfer files to/from Blacklight filesystems using the GridFTP server address "
gsiftp://gridftp.psc.xsede.org". This transfer will go through the PSC high-speed data conduit data.psc.xsede.org.
gsiftp:// URLs are absolute paths to files. This means that when referring to a file or directory in your Blacklight
$SCRATCH directory, you must use
joeuser is your Blacklight userid. Likewise, for your Blacklight
$HOME directory, you must use
List the files in my Blacklight
joeuser@tg-login1:~> globus-url-copy -list gsiftp://gridftp.psc.xsede.org/brashear/joeuser gsiftp://gridftp.psc.xsede.org/brashear/joeuser/ file1.dat file2.dat file3.dat newdata/ olddata/
Transfer a file (
testfile) from my scratch space on TACC lonestar to my PSC Blacklight
joeuser@tg-login1:~> globus-url-copy -stripe -tcp-bs 32M \ gsiftp://gridftp.lonestar.tacc.xsede.org/scratch/99999/tg987654/testfile \ gsiftp://gridftp.psc.xsede.org/brashear/joeuser/newdata/
-tcp-bs 32Mare used to improve transfer performance, and
/scratch/99999/tg987654is your scratch directory on lonestar at TACC.
If you have a current user proxy certificate you can also use
gsiscp to tranfer files to and from Blacklight. The method of obtaining a valid user proxy certificate is described above in the discussion of the
globus-url-copy command. The default directory for both
gsiscp is your Data Supercell home directory. Thus, to transfer files to and from Blacklight you must specify the full path to your Blacklight directory.
gsiscp session is:
gsisftp data.psc.xsede.org sftp> get /brashear/joeuser/file1.dat localfile1.dat Fetching /brashear/joeuser/file1.dat to /usr/local/projects/localfile1.dat /brashear/joeuser/file1.dat 100% 31 0.0KB/s 00:00 sftp> bye
gsiscp command is:
$ gsiscp data.psc.xsede.org:/brashear/joeuser/file1.dat localfile1.dat file1.dat 100% 1016KB 101.0 MB/s 00:00
To transfer files between the Data Supercell and Blacklight's file systems you can also use PSC's
far program. Far is available on all PSC production platforms. In addition to file transfers, the
far program can be used for file and directory management, such as getting a list of your files on the Data Supercell. See the
far documentation for more information. Globus is our recommended method for transferring data between Blacklight and the Data Supercell. The
far utility is being maintained for backward compatiblity with older scripts. At some time in the future it will not be supported.
We recommend that if you do use
far you execute your
far commands outside of your batch job scripts so that your jobs do not tie-up compute processors and you do not expend your computing allocation transferring files.
File transfer performance between your local systems and Blacklight filesystems can be significantly improved by ensuring that your local systems' networking parameters are optimized. Guidance is available at PSC's Enabling High Performance Data Transfers webpage.
For improved performance when using SSH (
scp), we recommend using an SSH package that includes PSC's High Performance Networking (HPN) patches, e.g., GSI-OpenSSH. For instructions to build OpenSSH with PSC's HPN patches, consult the PSC High Performance SSH/SCP - HPN-SSH webpage.
The Intel C, C++ and Fortran compilers and the GNU Fortran, C and C++ compilers are installed on Blacklight and they can be used to create OpenMP, pthreads, MPI, hybrid and serial programs. The commands you should use to create each of these types of programs are shown in the table below.
|Intel Fortran||ifort -openmp myopenmp.f90||ifort -pthread mypthread.f90||ifort mympi.f90 -lmpi||ifort -openmp myhybrid.f90 -lmpi||ifort myserial.f90|
|Intel C||icc -openmp myopenmp.c||icc -pthread mypthread.c||icc mympi.c -lmpi||icc -openmp myhybrid.c -lmpi||icc myserial.c|
|Intel C++||icpc -openmp myopenmp.cc||icpc -pthread mypthread.cc||icpc mympi.cc -lmpi -lmpi++||icpc -openmp myhyrid.cc -lmpi -lmpi++||icpc myserial.cc|
|GNU Fortran||gfortran -fopenmp myopenmp.f90||gfortran -pthread mypthread.f90||gfortran mympi.f90 -lmpi||gfortran -fopenmp myhybrid.f90 -lmpi||gfortran myserial.f90|
|GNU C||gcc -fopenmp myopenmp.c||gcc -pthread mypthread.c||gcc mympi.c -lmpi||gcc -fopenmp myhybrid.c -lmpi||gcc myserial.c|
|GNU C++||g++ -fopenmp myopenmp.cc||g++ -pthread mypthread.cc||g++ mympi.cc -lmpi -lmpi++||g++ -fopenmp myhybrid.cc -lmpi -lmpi++||g++ myserial.cc|
Man pages are available for
icpc and for
You should use the system-supplied SGI version of MPI. Thus, you should not use OpenMPI in your programs, even if you install your own version of OpenMPI. If the SGI version of MPI is inadequate for your needs send email to firstname.lastname@example.org.
The UPC compiler is installed on Blacklight. Online instructions are available for its use.
Two versions of Java are available on Blacklight: an IBM version and a Sun version. You should load the module for the version you want to use. If you issue the command:
$ module load java
you will load the Sun version. Once you load a Java module the Java compiler and interpreter will then be available to use. A java man page is also available.
Torque, an open source version of the Portable Batch System (PBS), controls all access to Blacklight's compute processors, for both batch and interactive jobs. Currently Blacklight has two queues: the batch queue and the debug queue. Interactive jobs can run in the debug queue and the batch queue and the method for doing so is discussed below.
Batch queue jobs can ask for a maximum of 168 hours of walltime.
The maximum walltime for jobs in the debug queue is 30 minutes. You must request 16 cores. The debug queue is not to be used for short production runs.
Jobs submitted to the batch queue are actually sent by the system into subqueues based on the their walltime and core requests. You only submit jobs directly into the batch queue.
Jobs that ask for 1440 or fewer cores and 48 or fewer hours are slotted into the
batch_r1 subqueues. Jobs that ask for more than 48 hours of walltime are slotted into the
batch_l1 subqueues. Jobs that request more than 1440 cores are slotted to a separate queue where they receive special handling.
You determine how much memory your job will be allocated through the value of your core request. The maximum number of cores a shared memory job can request is 2048. If you want to run a hybrid job using MPI and threads or a UPC job that needs more than 2048 cores send email to email@example.com to make special processing arrangements.
The batch queue is basically a FIFO queue. However, there are mechanisms in place to prevent a single user from dominating the batch queue and to prevent idle time on the machine. The result is some deviation from a strictly FIFO scheme.
We will modify the scheduling policies on Blacklight to meet user needs. If you have comments about the scheduling policies on Blacklight or find that they do not meet your needs send email to firstname.lastname@example.org.
To run a batch job on Blacklight you submit a batch script to the scheduler. A job script consists of PBS directives, comments and executable commands. The last line of your batch script must end with a newline.
#!/bin/csh #PBS -l ncpus=16 #ncpus must be a multiple of 16 #PBS -l walltime=5:00 #PBS -j oe #PBS -q batch set echo #move to my $SCRATCH directory cd $SCRATCH #copy executable to $SCRATCH cp $HOME/myopenmp . #run my executable setenv OMP_NUM_THREADS 16 omplace -nt $OMP_NUM_THREADS ./myopenmp
The first line in the script cannot be a PBS directive. Any PBS directive in the first line is ignored. Here, the first line identifies which shell should be used for your batch job.
The four #PBS lines are PBS directives.
- #PBS -l ncpus=16
- This directive determines the number of cores allocated to your job. For performance reasons the actual allocation of resources is done by blades, with each blade containing sixteen cores. Jobs do not share blades. **You must specify a value for ncpus that is a multiple of sixteen.** Within your batch script the environment variable `$PBS_NCPUS` is set to the value of ncpus. Each blade has 128 Gbytes of physical memory. If your job exceeds the amount of physical memory available to it--a job with a ncpus value of 64 will run on 4 blades and thus have 512 Gbytes of memory available to it--it will be killed by the system with a message similar to
PBS: Job killed: cpuset memory_pressure 10562 reached/exceeded limit 1 (numa memused is 134200964 kb)written to its stderr. A cpuset is the set of blades--cores and associated memory--assigned to your job. Memory pressure is a metric that indicates whether the processes on a blade are attempting to free up in-use memory on the blade to satisfy additional memory requests. Since this use of memory would result in significantly lower performance, a job that attempts to do this is killed by the system. For more information about cpusets and memory pressure see the man page man 4 cpuset. If this happens to your job you should resubmit it and ask for more cores. The output from the `ja` command, which is discussed below, can help you determine how many blades your job needs. If asking for more cores does not resolve this issue contact
. When you do so include your jobids and numa memused value from the error message in your email to remarks. Blacklight is a large-memory machine. Thus, the number of cores you select will often be determined by the amount of memory your program needs. Below is a table that gives the amount of memory available for representative numbers of requested cores. # Cores Memory (Gbytes) 16 128 64 512 256 2048 512 4096 1024 8192 1424 13952
- #PBS -l walltime=5:00
- The second directive requests 5 minutes of walltime. Specify the time in the format HH:MM:SS. At most two digits can be used for minutes and seconds. Do not use leading zeroes in your walltime specification.
- #PBS -j oe
- The next directive combines your .o and .e output into one file, in this case your .o file. This makes your job easier to debug. Your stdout and stderr files are each limited to 20 Mbytes if they are not redirected to a file. If your job exceeds either of these limits it will be killed by the system. If you have a program that you think will exceed either of these limits you should redirect either your stdout or stderr output or both to a `$SCRATCH` file. Moreover, unless you redirect your stdout and stderr output you cannot see it until your job ends.
- #PBS -q batch
- The final PBS directive requests that your job be run in the batch queue.
The remaining lines in the script are comments and command lines.
- set echo
- This command causes your batch output to display each command next to its corresponding output. This makes your job easier to debug. If you are using the Bourne shell or one of its descendants use `set -x` instead.
- Comment lines
- The other lines in the sample script that begin with '#' are comment lines. The '#' for comments and PBS directives must be in column one of your scripts.
- setenv OMP_NUM_THREADS 16
- This command sets the number of threads your OpenMP program will use. In the example, your program will have 1 thread per core, since you have requested 16 cores. You can also set the value of
$OMP_NUM_THREADSso that you have more than 1 thread per core. However, we have found that most threaded programs do not scale well above 32 threads, no matter how many cores you have requested. For most threaded programs 16 threads is an appropriate number to request. However, this number is application-dependent. You should test your application to see what the best number of threads is for your program.
omplace -nt $OMP_NUM_THREADS ./myopenmp
- This command runs your executable. The `omplace` command insures that your threads do not migrate across your cores.
#!/bin/csh #PBS -l ncpus=16 #ncpus must be a multiple of 16 #PBS -l walltime=5:00 #PBS -j oe #PBS -q batch set echo #move to my $SCRATCH directory cd $SCRATCH #copy executable to $SCRATCH cp $HOME/mypthread . #run my executable setenv OMP_NUM_THREADS 16 omplace -nt $OMP_NUM_THREADS ./mypthread
This script is identical to the OpenMP script, except for the name of the executable. The information about thread counts is also the same as for OpenMP programs.
#!/bin/csh #PBS -l ncpus=16 #ncpus must be a multiple of 16 #PBS -l walltime=5:00 #PBS -j oe #PBS -q batch set echo source /usr/share/modules/init/csh #move to my $SCRATCH directory cd $SCRATCH #copy executable to $SCRATCH cp $HOME/MyJavaApp.class . module load java #run my executable java -XX:ParallelGCThreads=16 MyJavaApp
This script is similar to the OpenMP script. The source command is needed because your job is using the module command. In place of the
omplace command you use the java interpreter to run your program.
The ParallelGCThreads option is used to specify the number of Java threads to generate for the purposes of garbarge collection. Normally for performance reasons you will generate one thread per core, although this is application dependent. In this example you are asking for 16 threads, which will give one thread per core. If you specify two threads per code your program will use hardware hyperthreads. You can specify more than 2 threads per core up to a maximum of 16 threads per core. If you need to use more than 16 threads per core send email to email@example.com.
If you are using the IBM version of Java the option to request 16 threads would be
java -Xgcthreads16 MyJavaApp
The Java system call
Runtime.getRuntime().availableProcessors() will always return 4096. To get the correct value for your number of cores you should instead call
System.getenv("PBS_NCPUS") and multiply the returned value by two.
#!/bin/csh #PBS -l ncpus=16 #ncpus must be a multiple of 16 #PBS -l walltime=5:00 #PBS -j oe #PBS -q batch set echo #move to my $SCRATCH directory cd $SCRATCH #copy executable to $SCRATCH cp $HOME/mympi . #run my executable mpirun -np $PBS_NCPUS ./mympi
This script is identical to the OpenMP script except when you run your executable. You do not have to set the variable
$OMP_NUM_THREADS, but you do have to use the mpirun command to launch your executable on Blacklight's compute processors. The value for the "
-np" option is the number of your MPI tasks. You should normally set "
$PBS_NCPUS. This will run each of your MPI tasks on its own core. If you want to use hyperthreading you should set the value of "
$PBS_HT_NCPUS. This will run two hardware threads on a single core. Whether this will improve the performance of your MPI program is application-dependent. It is unlikely that setting the value of "
-np" to a value greater than
$PBS_HT_NCPUS will improve the performance of your MPI program. You cannot currently request more than 16 threads per core. If you need to use more than 16 threads per core send email to firstname.lastname@example.org.
You must use mpirun to run your MPI executable. In addition, MPI programs will only run on Blacklight's compute nodes. Thus, they must be run using
#!/bin/csh #PBS -l ncpus=16 #ncpus must be a multiple of 16 #PBS -l walltime=5:00 #PBS -j oe #PBS -q batch set echo source /usr/share/modules/init/csh #move to my $SCRATCH directory cd $SCRATCH #copy executable to $SCRATCH cp $HOME/myupc . #load the UPC module module load sgi-upc #run my executable mpirun -np $PBS_NCPUS ./myupc
This script is identical to the MPI script above--other than the loading of the sgi-upc module and the associated source command--because SGI UPC uses MPI in its implementation. Thus, the above discussions of the mpirun command and threads apply to UPC jobs.
Information on compiling UPC programs is available online. If you load the sgi-upc module a man page is also available.
#!/bin/csh #PBS -l ncpus=256 #ncpus must be a multiple of 16 #PBS -l walltime=5:00 #PBS -j oe #PBS -q batch set echo #move to my $SCRATCH directory cd $SCRATCH #copy executable to $SCRATCH cp $HOME/myhybrid . #run my executable setenv OMP_NUM_THREADS 16 mpirun -np 16 omplace -nt 16 ./myhybrid
This script is identical to the above two scripts except when you run your executable. You use a combination of the mpirun and
omplace commands to run your hybrid program. The value of the "
-np" option to the mpirun command is the number of your MPI tasks. The value of the "
-nt" option to the
omplace command is the number of your OpenMP threads per MPI task. The value of the "
-nt" option and the value you set
$OMP_NUM_THREADS to must be the same. The product of the value of the "
-nt" option and the "
-np" option should be the value of your PBS ncpus specification, if you do not want to use hyperthreading. If you do want to use hyperthreading, the product of these two values should equal twice your ncpus value. To use hyperthreading you can use any values for "
-nt" and "
-np" as long as their product is twice your ncpus value. You can also choose values for "
-nt" and "
-np" such that their product is greater than twice your ncpus value. If you do this your first two threads per core will use hyperthreading. Which values you should select for "
-nt" and "
-np" is application dependent. You cannot currently request more than 16 threads per core. If you need to use more than 16 threads per core send email to email@example.com.
omplace command insures that each of your OpenMP threads do not migrate across your cores. You must use mpirun to run your hybrid executable or it will run on a frontend and degrade overall system performance.
#!/bin/csh #PBS -l ncpus=32 #ncpus must be a multiple of 16 #PBS -l walltime=5:00 #PBS -j oe #PBS -q batch set echo #move to my $SCRATCH directory cd $SCRATCH #copy executable to $SCRATCH cp $HOME/myserial . #run my executable ./myserial
To run a serial program you just give the name of your program as a statement in your batch script. Since you are running a serial program hyperthreading is not an issue. You use your ncpus paramater to ask for the number of cores you need so that you have enough memory in the blades allocated to your job for your program to run. Your serial program will have access to all the memory in all the blades allocated to your job. In the above example your program will have access to 256 Gbytes of memory.
After you create your batch script you submit it to PBS with the
qsub myscript.job Your batch output--your .o and .e files--is returned to the directory from which you issued the
qsub command after your job finishes.
You can also specify PBS directives as command-line options. Thus, you could omit the PBS directives from the first sample script above and submit the script with the command:
$ qsub -l ncpus=16 -l walltime=5:00 -j oe -q batch myscript.job
Command-line directives override directives in your scripts.
qsub options are available for specifying your job's walltime request.
-l walltime_min=HH:MM:SS -l walltime_max=HH:MM:SS
You can use these two options instead of "
-l walltime" to make your walltime request flexible or malleable. A flexible walltime request can improve your job's turnaround in several circumstances.
For example, to accommodate large jobs, the system actively drains blades to create dynamic reservations. The blades being drained for these reservations create backfill up to the reservation start time that may be used by other jobs. Using flexible walltime limits increases the opportunity for your job to run on backfill blades.
As an example, if your job requests 64 cores and a range of walltime between 2 and 4 hours and a 64-core slot is available for 3 hours, your job could run in this slot with a walltime request of 3 hours. If your job had asked for a fixed walltime request of 4 hours it would not be started.
Another situation in which specifying a flexible walltime could improve your turnaround is the period leading up to a full drain for system maintenance. The system will not start a job that will not finish before the system maintenance time begins. A job with a flexible walltime could start if the flexible walltime range overlaps the period when the maintenance time starts. A job with a fixed walltime that would not finish until after the maintenance period begins would not be started.
If the system starts one of your jobs with a flexible walltime request, the system selects a walltime within the two specified limits. This walltime will not change during your job's execution. You can determine the actual walltime your job was assigned by examining the "
Resource_List.walltime" field of the output of the "
qstat -f" command. The command:
$ qstat -f $PBS_JOBID
will give this output for the current job. You can capture this output to find the value of the
You may need to provide this value to your program so that your program can make appropriate decisions about writing checkpoint files. In the above example, you would tell your program that it is running for 3 hours and thus should begin writing checkpoint files sufficiently in advance of the 3-hour limit so that the file writing is completed when the limit is reached. The functions "
mpi_wtime" and "
omp_get_wtime" can be used to track how long your program has been running so that it writes checkpoint files to make sure you save results from your program's processing.
You may also want to save time at the end of your job to allow your job to transfer files after your program ends but before your job ends. You can use the timeout command to specify in seconds how long you want your program to run. Once your job determines what its actual walltime is you can, after subtracting the amount of time you want for file transfer at the end of your job, use this value in a timeout command. For example, assume your job is assigned a walltime of 1 hour and you want your program to stop 10 minutes before your job ends to allow your job to have adequate time for file transfer. To accomplish this you could use a command like the following:
timeout --timeout=$PROGRAM_TIME -- mpirun -np 32 ./mympi
The example assumes that your script has retrieved your job's walltime, converted it to seconds--values given to timeout must be in seconds--subtracted 600 from it and assigned the value of 3000 to the variable
$PROGRAM_TIME. You will probably also want to provide this value to your program. Your program can then use this value to appropriately write out checkpoint files. When your program ends your job will have time to perform necessary file transfers before your job ends.
For more information on the timeout command see the timeout man page. If you want assistance on the procedures needed to capture your job's actual walltime or to determine when your job should write checkpoint files send email to firstname.lastname@example.org.
We have several suggestions for how to improve your job turnaround. Firstly, you should try to be as accurate as possible in estimating the walltime request for your job. Asking for more time than your job will actually need will almost certainly result in poorer turnaround for your job. Thus, unreflectively asking for the maximum walltime you can ask for a job will almost always result in poorer turnaround.
Our second recommendation is that you always use flexible walltime requests if possible. This is especially helpful if your minimum walltime in your pair of walltime values is less than 8 hours.
Finally, due to system limitations, we must limit the number of concurrent 16-core jobs on Blacklight. Since the number of queued 16-core jobs usually is above this limit, if you are running 16-core jobs, it is to your advantage to pack multiple 16-core executions into a single job. How to pack jobs is discussed below.
A form of interactive access is available on Blacklight by using the "
-I" option to
qsub. For example, the command:
$ qsub -I -l ncpus=16 -l walltime=5:00
requests interactive access to 16 cores for 5 minutes in the. Your
qsub -I request will wait until it can be satisfied. If you want to cancel your request you should type ^C.
When you get your shell prompt back your interactive job is ready to start. At this point any commands you enter will be run as if you had entered them in a batch script. Stdin, stdout, and stderr are connected to your terminal. To run an MPI or hybrid program you must use the mpirun command just as you would in a batch script.
When you finish your interactive session type ^D. When you use
qsub -I you are charged for the entire time you hold your processors whether you are computing or not. Thus, as soon as you are done executing commands you should type ^D.
In order to use any X-11 tool, you must also include "
-X" on the
qsub command line:
$ qsub -X -I -l ncpus=16 -l walltime=5:00
This assumes that the
$DISPLAY variable is set. Two ways in which
$DISPLAY is automatically set for you are:
- Connecting to Blacklight with
ssh -X Blacklight.psc.teragrid.org
- Enabling X-11 tunneling in your Windows
Fluent and TAU are among the packages which require X-11 connections.
Besides those options mentioned above, there are several other options to
qsub that may be useful. See man
qsub for a complete list.
- -m a|b|e|n
- Defines the conditions under which a mail message will be sent about a job. If "a", mail is sent when the job is aborted by the system. If "b", mail is sent when the job begins execution. If "e", mail is sent when the job ends. If "n",no mail is sent. This is the default.
- -M userlist
- Specifies the users to receive mail about the job. Userlist is a comma-separated list of email addresses. If omitted, it defaults to the user submitting the job. You should specify your full Internet email address when using the -M option.
- -v variable_list
- This option exports those environment variables named in the variable_list to the environment of your batch job. The -V option, which exports all your environment variables, has been disabled on Blacklight.
- -r y|n
- Indicates whether or not a job should be automatically restarted if it fails due to a system problem. The default is to not restart the job. Note that a job which fails because of a problem in the job itself will not be restarted.
- -W group_list=charge_id
- Indicates to which charge_id you want a job to be charged. If you only have one allocation on Blacklight you do not need to use this option; otherwise, you should charge each job to the appropriate allocation. You can see your valid charge_ids by typing `groups` at the Blacklight prompt. Typical output will look like
sy2be6n ec3l53p eb3267p jb3l60qYour default charge_id is the first group in the list; in this example "sy2be6n". If you do not specify `-W group_list` for your job, this is the allocation that will be charged.
- -W depend=dependency:jobid
- Specifies how the execution of this job depends on the status of other jobs. Some values for dependencyare:
Specifying "before" dependencies requires that job jobid be submitted with -W depend=on:count. See the man page for details on this and other dependencies.
after this job can be scheduled after job jobid begins execution. afterok this job can be scheduled after job jobid finishes successfully. afternotok this job can be scheduled after job jobid finishes unsucessfully. afterany this job can be scheduled after job jobid finishes in any state. before this job must begin execution before job jobid can be scheduled. beforeok this job must finish successfully before job jobid begins beforenotok this job must finish unsuccessfully before job jobid begins beforeany this job must finish in any state before job jobid begins
Running many small jobs places a great burden on the scheduler and is probably inconvenient for you. An alternative is to pack many executions into a single job, which you then submit to PBS with a single
qsub command. The basic method to use to pack jobs is to run each program execution in the background and place a wait command after all your executions. A sample job to pack serial executions is:
#!/bin/csh #PBS -l ncpus=128 #ncpus must be a multiple of 16 #PBS -l walltime=5:00 #PBS -j oe #PBS -q batch set echo #move to my $SCRATCH directory cd $SCRATCH #copy executables and input files to $SCRATCH cp $HOME/myserial* . cp $HOME/serial* . #run my executables dplace -c 0 ./myserial1 > serial1.out < serial1.dat & dplace -c 32 ./myserial2 > serial2.out < serial2.dat & dplace -c 64 ./myserial3 > serial3.out < serial3.dat & dplace -c 96 ./myserial4 > serial4.out < serial4.dat & wait
Each serial execution will run on 2 blades. The
dplace command insures that each execution will run on its own set of 2 blades. The executions will run concurrently.
To pack a job with executables that use threads such as OpenMP executables you should replace the
dplace command with the
omplace command. A sample job to pack OpenMP executables is:
#!/bin/csh #PBS -l ncpus=128 #ncpus must be a multiple of 16 #PBS -l walltime=5:00 #PBS -j oe #PBS -q batch set echo #move to my $SCRATCH directory cd $SCRATCH #copy executables and input files to $SCRATCH cp $HOME/myopen* . #run my executables omplace -nt 32 -c 0 ./myopenmp1 > openmp1.out < openmp1.dat & omplace -nt 32 -c 32 ./myopenmp2 > openmp2.out < openmp2.dat & omplace -nt 32 -c 64 ./myopenmp3 > openmp3.out < openmp3.dat & omplace -nt -32 -c 96 ./myopenmp4 > openmp4.out < openmp4.dat & wait
A sample job to pack MPI executables is:
#!/bin/csh #PBS -l ncpus=64 #ncpus must be a multiple of 16 #PBS -l walltime=5:00 #PBS -j oe #PBS -q batch set echo #move to my $SCRATCH directory cd $SCRATCH #copy executables and input files to $SCRATCH cp $HOME/mympi* . #run my executable mpirun -np 16 dplace -c 0-15 ./mympi > mpi1.out < mpi1.dat & mpirun -np 16 dplace -c 16-31 ./mympi > mpi2.out < mpi2.dat & mpirun -np 16 dplace -c 42-47 ./mympi > mpi3.out < mpi3.dat & mpirun -np 16 dplace -c 48-63 ./mympi > mpi4.out < mpi4.dat & wait
Packing jobs is especially useful to do if you are running 16-core jobs. Due to system limitations, we must limit the number of concurrent 16-core jobs on Blacklight. Since the number of queued 16-core jobs usually exceeds this limit, if you are running 16-core jobs, it is to your advantage to pack multiple 16-core executions into a single job.
If you have questions about packing jobs send email to email@example.com. For more information about
omplace see the man pages for
qstat -a" command displays the status of the queues. It shows running and queued jobs. For each job it shows the amount of walltime and the number of cores and processors requested. To get the actual number of cores a job is using you must divide the displayed value by two. For running jobs it shows the amount of walltime the job has already used
The commands "
qstat -s", "
qstat -f" and "
pbsnodes -a" can be used to give status information about the system and your jobs. The comments that these commands provide can be used to determine why your jobs have not started. The "
qstat -f" command take a jobid as an argument.
qdel command is used to kill queued and running jobs. An example is the command:
$ qdel 54
The argument to
qdel is the jobid of the job you want to kill, which you are shown when you submit your job or you can get it with the qstat command. If you cannot kill a job you want to kill send email to firstname.lastname@example.org.
Your first few runs should be on a small version of your problem. Your first run should not be for your largest problem size. It is easier to solve code problems if you are using fewer processors. This strategy should be followed even if you are porting a working code from another system.
Do not run a debugging run on any of Blacklight's front ends. You should always run a Blacklight program with
gdb debuggers are available on Blacklight. The
gdb debugger has a man page. Information for
idb is available online. This online documentation has links to more
idb reference material. Send email to email@example.com if you want another debugger to be installed.
Several compiler options can be useful to you when you are debugging your program. If you use the "
-g" option to the Intel or GNU compilers, the error messages you receive when your program fails will probably be more informative. For example, you will probably be given the line number of the source code statement that caused the failure. Once you have a production version of your code you should not use the -g`" option or your program will run slower.
The -check bounds option to the
ifort compiler will cause your program to tell you if it exceeds an array bounds while running.
Variables on Blacklight are not automatically initialized. This can cause your program to fail if it relies on variables being initialized. The -check uninit and -ftrupuv options to the
ifort compiler will catch certain cases of uninitialized variables, as will the -Wall and -O options to the GNU compilers.
There are more options to the Intel and GNU compilers that may assist you in your debugging. For more information see the appropriate man pages.
The key to making core files on Blacklight is to allow them to be written by increasing the maximum file size allowable for core files. The default size is 0 bytes. If you are using sh-type shells you do this by issuing the command:
$ ulimit -c unlimited
For csh-type shells you issue the command:
$ limit coredumpsize unlimited
Core files are created in directory ~/tmp. For more information about core files issue the command:
$ man 5 core
The data bytes in a binary floating point number or a binary integer can be stored in a different order on different machines. Blacklight is a little endian machine, which means that the low-order byte of a number is stored in the memory location with the lowest address for that number while the high-order byte is stored in the highest address for that number. The data bytes are stored in the reverse order on a big endian machine.
If your machine has Tcl installed you can tell whether the machine is little endian or big endian by issuing the command:
$ echo 'puts $tcl_platform(byteOrder)' | tclsh
You can read a big endian file on Blacklight if you are using the Intel
ifort compiler. Before you run your program issue the command:
$ setenv FORT_CONVERTn big_endian
for each Fortran unit number from which you are reading a big endian file. For 'n' substitute the appropriate unit number.
You can calculate your code's Mflops rate using the TAU utility. The TAU examples show how to determine timing data and floating point operation counts for your program, from which you can calculate your Mflops rate.
Cache performance can have a significant impact on the performance of your program. Each Blacklight core has three levels of cache. The primary data and instruction caches are 32 Kbytes each. The L2 cache is 256 Kbytes. The L3 cache, which is shared by the 8 processors on a core, is 24 Mbytes. When hyper-threading is enabled the two threads on a core share the L1 and L2 caches.
You can measure your program's cache miss rate for each of the available caches by setting the appropriate counters when using the TAU utility. If you need assistance in measuring or improving your cache performance send email to firstname.lastname@example.org.
Blacklight's Nehalem processors have a feature referred to as Turbo Boost. Under certain workload conditions its processor cores can automatically and dynamically run faster than their base clockrate of 2.27 GHz. Although the activation of the Turbo Boost feature is application dependent, we have found that it is most often activiated when only a few cores per processor are being used, because its activation depends on the processor's power consumption and temperature.
Collecting timing data is essential for measuring and improving program performance. We recommend five approaches for collecting timing data. The ja and /usr/bin/time utilities can be used to collect data at the program level. They report results to the hundredths of seconds. The TAU utility and the
MPI_Wtime functions can be used to collect timing data at a finer grain. The default precision for TAU is microseconds, but the -linuxtimers or -papi option can be used to obtain nanosecond precision. The precision for
omp_get_wtime is microseconds, while the precision for
MPI_Wtime is nanoseconds.
The ja command turns on job accounting for your job. This allows you to obtain information on the elapsed time and memory and IO usage of your program, plus other data. You should place the ja command in your batch script after your PBS specifications and before your executable commands.
You must pair your initial ja command with another ja command at the end of your job. We recommend you use the command ja -chlst for this second command. The option "
-t" to this second ja command turns off job accounting and writes your accounting data to stdout. The other options to the second ja command determine what output you will receive from ja. We recommend the -chls options because we think they will provide detailed but useful information about your job's processes. However, you can look at the man page for ja to see what reporting options you want to use.
There is no overhead to using ja. We strongly recommend you use ja when you want to understand the resource usage of your jobs. You can use this information when you submit future jobs. The output from ja can also be used for debugging and performance improvement purposes.
If your job terminates normally and you have included the "
-t" option with your second ja command, your ja output is written to your job's stdout. If you have any questions about using ja or encounter any errors when running ja send email to email@example.com.
Blacklight's operating system creates a file system out of its blade memory. Thus, your program can perform IO to blade memory rather than to disk. Memory IO is several orders of magnitude faster than disk IO. However, each Blacklight job can only perform memory IO to the blades associated with that job. A job cannot write to the memory of blades assigned to other jobs.
The environment variable
$SCRATCH_RAMDISK is set to point to the memory associated with each job. Unlike
$SCRATCH, this variable is given a new value for each job. Otherwise, this variable can be treated like
$SCRATCH. From within your job, you can cd to it, you can copy files to and from it, and you can use it to open files.
Memory IO is faster than disk IO, but it does have disadvantages. Each job's memory filespace is cleared whenever the job terminates, whether normally or abnormally. Thus, if you are using memory IO you must copy your memory files back from
$SCRATCH_RAMDISK before your job ends or the files are lost. If your job terminates abnormally your files will be lost. Moreover, memory IO is limited in size relative to disk IO. Each job can only use the memory associated with that job. Furthermore, memory IO is limited to the memory available after memory is allocated for your program. Moreover, the largest size a single memory file can be is 256 Gbytes. Therefore, the use of memory files is best suited to IO-intensive jobs that perform IO to lots of small files.
If your program reads or writes large files you should use
$HOME space is limited. In addition, the
$SCRATCH file space is implemented using the Lustre parallel file system. A program that uses
$SCRATCH can perform parallel IO and thus can significantly improve its performance. File striping can be used to tune your parallel IO performance and is particularly effective for files that are 1 Gbyte or larger.
A Lustre file system is created from an underlying set of file systems called Object Storage Targets (OSTs). Your program can read from and write to multiple OSTs concurrently. This is how you can use Lustre as a parallel file system.
A striped file is one that is spread across multiple OSTs. Thus, striping a file is one way for you to be able to use multiple OSTs concurrently. However, striping is not suitable for all files. Whether it is appropriate for a file depends on the IO structure of your program.
For example, if each of your cores writes to its own file you should not stripe these files. If each file is placed on its own OST then as each core writes to its own file you will achieve a concurrent use of the OSTs because of the IO structure of your program. File striping in this case could actually lead to an IO performance degradation because of the contention between the cores as they perform IO to the pieces of their files spread across the OSTs.
An application ideally suited to file striping would be one in which there is a large volume of IO but a single core performs all the IO. In this situation you will need to use striping to be able to use multiple OSTs concurrently.
However, there are other disadvantages besides possible IO contention to striping and these must be considered when making your striping decisions. Many interactive file commands such as "
ls -l" or unlink will take longer for striped files.
You use the lfs setstripe command to set the striping parameters for a file. You have to set the striping parameters for a file before you create it.
The format of the lfs setstripe command is:
$ lfs setstripe filename -c stripe-count
A value of -1 for the stripe count means the file should be spread across all the available OSTs.
For example, the command:
$ lfs setstripe bigfile.out -c -1
sets the stripe count for bigfile.out to be all available OSTs.
$ lfs setstripe manyfiles.out -c 1
has a stripe count of 1. Each file will be placed on its own OST. This is suitable for the situation where each core writes its own file and you do not want to stripe these files.
You can also specify a directory instead of a filename in the lfs setstripe command. The result will be that each file created in that directory will have the indicated striping. You can override this striping by issuing an lfs setstripe command for individual files within that directory.
The kind of striping that is best for your files is very application dependent. Your application will probably fall between the two extreme cases discussed above. You will therefore need to experiment with several approaches to see which is best for your application. A value of -1 for stripe count will probably give you the best performance if you are going to use file striping, but you should try several values. The maximum value you can give for stripe count on Blacklight is currently 8.
Third-party routines can often perform better than routines you code yourself. You should investigate whether there is a third-party routine available to replace any of the routines you have written yourself.
We have installed several performance monitoring tools on Blacklight. The TAU utility is a performance profiling and tracing tool. The PAPI utility can be used to access the hardware performance counters on Blacklight. We intend to install more performance tools on Blacklight. If you want assistance in using any of these tools or have a utility you would like us to install send email to firstname.lastname@example.org.
Blacklight is a very large hardware-coherent shared memory machine. Blacklight is thus suitable for a range of memory-intensive computations that cannot readily be deployed on a distributed-memory machine.
PSC has established the Memory Advantage Program (MAP) to enable users to take advantage of Blacklight's unique capabilities. MAP includes consulting assistance from PSC, special queue handling if necessary and service unit discounts.
To participate in MAP you should send an email to email@example.com with a description of your scientific problem and any information you have on how effectively your program is currently using Blacklight's shared memory. A PSC Scientific Specialist will then contact you to troubleshoot problems, provide advice on the use of debugging and performance analysis tools and procedures, and offer suggestions on fixes and optimizations. During this consultation process you will be able to make benchmarking, debugging and test runs at a 50% discount for a period of up to 4 weeks.
You can also send email to firstname.lastname@example.org if you want optimization assistance in areas other than memory usage.
Just getting an account on Blacklight is not sufficient to give you access to Gaussian if you want to use Gaussian. You must fill out our online PSC Gaussian User Agreement to get access to Gaussian at PSC.
If you have questions about access to Gaussian send email to email@example.com.
Before you can run many software packages, you must define paths and other environment variables. To use a different version of a package, these definitions often have to be modified. The module command makes this process easier. For use of the module command, including its use in batch jobs, see the module documentation.
As a user of Blacklight, it is imperative that you stay informed of changes to the machine's environment. Refer to this document frequently.
You will also periodically receive email from PSC with information about Blacklight. In order to insure that you receive this email, you should make sure your email forwarding is set properly by following the instructions for setting your email forwarding.
PSC requests that a copy of any publication (preprint or reprint) resulting from research done on Blacklight be sent to the PSC Allocations Coordinator. In addition, if your research was funded by the NSF you should log your publications at the XSEDE Portal. We also request that you include an acknowledgement of PSC in your publication.
You have several options for reporting problems on Blacklight.
- If you are an XSEDE user you can send email to firstname.lastname@example.org, mentioning PSC in the subject line. You will get an acknowledgement from the XSEDE Operations Center, and then you will be contacted by PSC staff.
- You can call the User Services Hotline at 412-268-6350 from 9:00 a.m. until 5:00 p.m., Eastern time, Monday through Friday.
Last update: September 21, 2014