You are here

Notices on Use

User Account

You cannot share the user account with anyone. Do not let other person to use your account.
User account can be added/removed after the approval of the application.

File System Usage

Avoid creating massive number of files

Distributed file system is not good at handling numerous files (especially if these files are in the single directory).
If you need to keep many small files, you would be better off combining them into single file with "tar" command.
Moreover, you can save disk space by compressing that combined (archived) file using "gzip" or others.

Avoid accessing single large file from many processes

This type of operation can result in significant performance degradation of overall storage.
For example, if 500 of jobs (processes) try to read single 100 GB file simultaneously, it would cause overall system trouble.
We request you to avoid this type of file access. If you found this type access is inevitable, please ask us first.

Avoid massive write to stdout/stderr of jobs

Contents of job stdout/stderr are stored in disk of the computation node(s), and then copied to specified directory (default: working directory) after the termination of the job. Massive write to stdout/stderr might cause unexpected termination of job or an error upon file copy in the last stage.

Storage Types

There are following disk types. Use them wisely.

name backup data retention period disk
/home NO 1 year after the end of use YES There are no differences other than name between /home and /save now.
/work NO only during job is running NO temporary disk space for jobs
  • Retention period may be extended if enough disk space is available.


System Trouble and CPU Points

Once system trouble (hardware/software) happend, jobs can be killed/stopped by the system. In this case, CPU points for these jobs won't be consumed.
If the job was restarted after the unexpceted system crash, CPU points will be billed only for the restart run.

Running Programs on Front-end Servers

You can run short test jobs and data analysis calculations directly on the front-end servers. For this purpose, setting of front-end servers is equivalent to that of computation nodes.
However, there are some restrictions.

  • We will kill processes using huge resources for long time or processes causing troubles to others without any warning.
  • You cannot expect for a comparable performance to computation nodes due to the special limitations on front-end servers.
    • Performance evaluation should be done at computation nodes.