Saldo Command

The CSC environment offers the saldo command for monitoring your project's usage of CSC's computing resources. Computing resources are shared by the project, i.e. members of the project use resources in common.

Using the saldo command

To run saldo in the CSC computing environment, give the unix command saldo. The saldo utility prints user's projects' total usage of CSC resources, and project members' monthly usage on each different servers in both billing units (bu) and CPU seconds.

Below is shown the output of saldo, which shows the usage of a sample project on 16.6.2015 at 8:15 AM. The project's code is csc2051, and name New models from wire. The project manager is Pekka Investigator, and the users are pinvest, ppostdoc and astudent (if the user has not used any resources, their usage is not printed). The project has started on 7.8.2014, and will end on 7.8.2016. The last grant of computing resources was made on 1.6.2015.

saldo (or alternatively: saldo -p csc2051 -m 6)
Saldo for year 2015 month 6
Report updated 16.06.2015 8:15
Project csc2051   New models from wire   Pekka Investigator
start 07.08.2014      end: 07.08.2016       budget: 01.06.2015
CSC budget: 2557574   used: 1797834         remain: 759740
         Cpu usage          Cpu secs     Bu
csc2051  pinvest            24066000  13370 taito
         pinvest    Tot     24066000  13370

csc2051  ppostdoc          979023600 543902 sisu
         ppostdoc   Tot    979023600 543902

csc2051  astudent          128622600  71457 pouta
         astudent   Tot    128622600  71457

         Cpu        total 1131712200 628729


Figure: Saldo print for the project csc2051 (on 16.6.2015). It is advisable that Pekka Investigator applies for more CPU time for his project, because the current compute resources will be used up soon.

Contents of the saldo print:

  • CSC budget: Cumulative project quota from the beginning of the year (2557574 billing units, bu)
  • used: Cumulative project usage from the beginning of the year (1797843 bu)
  • remain: Remaining computing resources of the project at the time saldo was updated (759740 bu)
  • Cpu usage (monthly listing per user and per server):
    • The monthly usage of all active members of the project: project, userid, their usage in CPU seconds (CPU secs) and billing units (Bu), and the used server
    • At the bottom is shown the project's monthly total usage in CPU seconds and billing units.


Saldo has the following options available:

  • -p projid prints a saldo report for the selected project. This option is helpful if you belong to several projects.
  • -m month can have values between 1–12. You can print the usage of the selected month up to one year backwards. E.g. saldo -p csc2051 -m 1 prints the project usage from January.
  • -h filename generates an HTML file of the report.


  • saldo [ -m month ] [ -p projid ] [ -h filename ]

Monitoring the CPU time usage

Billing unit (bu) is the reference point of the CSC computing environment for academic use, and is based on one CPU hour of the old Cray XT4 supercomputer ( Billing units in the CSC environment are derived from benchmark testing of servers.

  • On old Cray XT4 a job that used one processor core and lasted one hour consumed one billing unit (bu), i.e., 1 core-h = 1 bu.
  • Sisu, Taito and cPouta consume two billing units per core hour, i.e. 1 core-h on Sisu, Taito or Pouta = 2 bu.
  • Memory is billed on Taito: billing units = 2 x max (number of reserved cores, ceiling(amount of reserved memory in GB / 4)) x runtime in hours

Note that accounting is based on reserved cores and memory.

For Taito the basis of billing is either the number of cores or number (rounded up to the nearest integer) of 4 GB blocks of memory, depending which is larger. For example,

  • an 8 core job with 16 GB of memory will be billed with 2 x 8 = 16 billing units per hour
  • an 8 core job with 64 GB of memory will be billed with 2 x 16 = 32 billing units per hour

Saldo updates

In the CSC environment, the saldos of customer projects are updated hourly. This means that the allocated resources are not added immediately, but within an hour.

Saldo report only contains data from completed batch jobs. The jobs in batch queue or running are not yet included in the report.

Using up computing resources

When the project's compute resources drop below 20% of the cumulative CSC budget, you will receive an automatic warning:

ATTENTION: You have less than 20% CPU time quota left on your default
account. Please apply for more CPU time quota.

It is advisable to apply for more CPU time for your project well before the current compute resources are used up. However, those jobs that are already running are completed, even though the project quota becomes negative during the run. When the quota is negative, new batch jobs cannot be submitted until you have applied for and have been granted new computing quota.

See also