Performance tools Pt2 - static vs dynamic linking

Brendan Bouffler
Date : February 16, 2024
Categories : AI/ML ,AWS Batch ,AWS ParallelCluster ,Amazon NICE DCV ,Elastic Fabric Adapter ,Life Sciences
Tags : ai ml ,aws ,batch ,cpus ,dcv ,ec2 ,efa ,gpus ,hpc ,high performance computing ,lustre ,mpi ,nccl ,parallel cluster ,schedulers ,storage ,autoscaling ,aws batch ,bioinformatics ,cloud computing ,dynamic linking ,elastic ,elastic fabric adapter ,hacks ,hpc instances ,infiniband ,job scheduling ,performance ,scientific computing ,static linking ,supercomputing ,technical computing ,tightly coupled ,virtualization ,vizualization ,techshorts

Welcome to the world of dynamically linked libraries and all the fun involved in predicting - and then manipulating - which libraries your binaries see and use … all so you can get the results and performance you expect.

Dr Stephen Sachs from our performance engineering team lives in this world every day, and gave up a bunch of his time to help the Tech Shorts community understand how to use all these tools.

Part 1: readelf, nm, strings, ldd, objdump Part 2: static vs dynamic linking Part 3: RPATH and RUNPATH - manipulating which libraries your executable sees. Part 4: let’s hack a binary to show you how this all works in practice.

If you have ideas for technical topics you’d like to see us cover in a future show, let us know by emailing us at ask-hpc@amazon.com.