หน้านี้ยังไม่พร้อมใช้งานในภาษาท้องถิ่นของคุณ เรากำลังพยายามอย่างหนักเพื่อเพิ่มเวอร์ชันภาษาอื่น ๆ เพิ่มเติม ขอบคุณสำหรับการสนับสนุนเสมอมา

Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
Software Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

HPC Resumable Computing Solution

Updated on 2022-05-09 GMT+08:00

Scenarios

Many HPC applications support resumable computing, such as LAMMPS and GROMACS. In addition, common HPC scheduling software can have resumable computing integrated, such as PBS, Slurm, and LSF.

This section uses LAMMPS as an example to describe how to perform HPC resumable computing.

Step 1: Install FFTW

Run the following commands to install FFTW:

yum install gcc-gfortran gcc-c++

wget http://www.fftw.org/fftw-3.3.8.tar.gz

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/mpi/gcc/openmpi-2.1.2a1/lib64/

export PATH=/usr/mpi/gcc/openmpi-2.1.2a1/bin:$PATH

tar -zxvf fftw-3.3.8.tar.gz

cd fftw-3.3.8/

./configure --prefix=/opt/fftw CC=gcc MPICC=mpicc --enable-mpi --enable-openmp --enable-threads --enable-avx --enable-shared

make && make install

Step 2: Install LAMMPS

  1. Run the following commands to install LAMMPS:

    yum install libjpeg-*

    yum install libpng12-*

    wget https://lammps.sandia.gov/tars/lammps-2Aug18.tar.gz

    tar -zxvf lammps-2Aug18.tar.gz

    cd lammps-2Aug18/src

    vi MAKE/Makefile.mpi

  2. Modify the data marked in red boxes in Figure 1 and Figure 2. Change the version based on site requirements.
    NOTICE:

    Modify only the data marked in red boxes in Figure 1 and Figure 2.

    Figure 1 Modifying the Makefile file 1
    Figure 2 Modifying the Makefile file 2
  3. Run the following command to compile LAMMPS and copy the obtained lmp_mpi file to /share:

    make mpi

Step 3: Configure LAMMPS

  1. Configure the example input file.

    Melt is used as an example to generate example file melt.in. For example, a checkpoint file is automatically generated for every 100 iterative operations, and the file is stored in /share. The file is as follows:

    # 3d Lennard-Jones melt
     
    units           lj
    atom_style      atomic
     
    lattice         fcc 0.8442
    region          box block 0 20 0 20 0 20
    create_box      1 box
    create_atoms    1 box
    mass            1 1.0
     
    velocity        all create 1.44 87287 loop geom
     
    pair_style      lj/cut 2.5
    pair_coeff      1 1 1.0 1.0 2.5
     
    neighbor        0.3 bin
    neigh_modify    delay 5 every 1
     
    fix             1 all nve
    dump 1 all xyz 100 /share/sample.xyz
    run             10000 every 100 "write_restart /share/lennard.restart"
  2. Obtain the melt.restart.in input file for resumable checkpoint computing.
    # 3d Lennard-Jones melt
     
    read_restart  /share/lennard.restart
    run        10000 every 100 "write_restart /share/lennard.restart"
  3. Obtain the PBS job script job.pbs.
    #!/bin/sh
    #PBS -l ncpus=2
    #PBS -o lammps_pbs.log
    #PBS -j oe
     
    export PATH=/usr/mpi/gcc/openmpi-2.1.2a1/bin:$PATH
     
    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/mpi/gcc/openmpi-2.1.2a1/lib64/module 
     
    if [ ! -e "/share/lennard.restart" ]; then
      echo "run at the beginning"
      mpiexec --allow-run-as-root -np 2 /share/lmp_mpi -in /share/melt.in
    else
      echo "run from the last checkpoint"
      mpiexec --allow-run-as-root -np 2 /share/lmp_mpi -in /share/melt.restart.in
    fi

Step 4: Submit a Job and Ensure that the Job Is Not Interrupted During Running

Submit and run the job without interrupting it, and check the job running duration.

  1. Run the following command to submit a job:

    qsub job.pbs

  2. After the job is complete, run the following command to view the job information:

    qstat -f Job ID

    As shown in Figure 3, the job runs for 4 minutes and 10 seconds.

    Figure 3 Job running without being interrupted

Step 5: Submit a Job, Emulate a Computing Interrupt, and Use Resumable Computing to Complete the Computing

After submitting a job, stop the compute node to emulate a computing interruption. Then, check the job running durations before and after the interruption.

  1. Run the following command to submit a job:

    qsub job.pbs

  2. After the job runs for about 1 minute and 30 seconds, stop the compute node on which the job runs to emulate example release.
  3. Run the following command to check the job information after the compute node is stopped:

    qstat -f Job ID

    Figure 4 Job running before interruption

    In such a case, the job returns back to the queued state, waiting for available computing resources.

  4. Start the compute node to provide available computing resources.

    In such a case, the job will continue.

  5. After the job is complete, run the following command to view the job information:

    qstat -f Job ID

    As shown in Figure 5, the job runs for 3 minutes and 3 seconds. It is shown that the job computing is resumed at the time when the computing is interrupted.

    Figure 5 Job running after interruption

เราใช้คุกกี้เพื่อปรับปรุงไซต์และประสบการณ์การใช้ของคุณ การเรียกดูเว็บไซต์ของเราต่อแสดงว่าคุณยอมรับนโยบายคุกกี้ของเรา เรียนรู้เพิ่มเติม

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback