GPU Resource Management On JDOS 梁永清 liangyongqing1@jd.com 提供的服务 1. 用于实验的 GPU 容器 2.基于 Kubeflow 的机器学习训练服务 3.模型管理和模型 Serving 服务 Experiment Training Serving 均基于容器，不对业务方直接提供 GPU 物理机 GPU 实验 JDOS 常规的容器服务

Securing the Foundations of the Rust Programming Language Coq Proof Assistant: A Formal Proof Management System built on top of built on top of Rust Types Overview Background T &mut T &T mutable alias. P ∗ Q Separation Logic (Iris) P Q v x y P −∗ Q Magic wand Consuming resource “P”, we can reach resource “Q”. Q P what we acually own Logics (x ↦ v) ∗ (x ↦ w) ⟹ False (x ↦ v) ∧ (x

Resource orchestration optimization of kubernetes cluster in large scale Patrickxie ( 谢谆志） Background Cloud has been the general trend. How to manage so many clusters ,resources and businesses How to ensure load balancing of cluster nodes 1 2 Improper resource requests 3 Multi-tenant resource preemption How to expand horizontally more quickly and flexibly 4 Region1 How do you manage K8S scheduling is based on the resource request of Pod. However, in many cases, some nodes have low resource requests but high load, while some nodes have high resource requests but low load. Dynamic-Scheduler

C++17: • std::pmr::memory_resource • std::pmr::polymorphic_allocator • std::pmr::vector • std::pmr::monotonic_buffer_resource • … std::pmr 16 |// gpu unified_memory_resource mem; std::pmr::vector std::pmr::vector y(N, &mem); // … Memory Allocation 17 |struct unified_memory_resource : std::pmr::memory_resource { void* do_allocate(std::size_t, std::size_t); void do_deallocate( do_is_equal( const std::pmr::memory_resource& other) const noexcept; }; A Unified Memory Resource 18 |struct unified_memory_resource : std::pmr::memory_resource { void* do_allocate(std::size_t

under synchronization/Hazptr.h Is Asynchronous Reclamation Always Enough? delete ptr shutdown_resource_X() Hazard Pointer Synchronous Reclamation Beyond Concurrency TS2 – Maged Michael Example: Removed reclamation ~Foo() { use_resource_X (); } Foo* ptr = new Foo; Remove ptr Is Asynchronous Reclamation Always Enough? No Asynchronous reclamation: delete ptr Using unavailable resource X Hazard Pointer Synchronous Michael Same example but using hazard pointer deferred reclamation ptr-retire() shutdown_resource_X() ~Foo() { use_resource_X (); } Foo* ptr = new Foo; Remove ptr Some use cases need synchronous reclamation

in Software Engineering Mike Ballou“There is no single development, in either technology or management technique, which by itself promises even one order-of- magnitude improvement within a decade abstract away its complexity often abstract away its essence • Not only technical problems but management problems as well comes from the complexity • It creates the tremendous learning and understanding I can help them I need…” • to Containerize the software, but to run that I need… • a Container Management Platform, but to network it I need… • a Service Mesh, but to secure it I need… • an automated Certificate

Helm Chart Support • Helm Chart repository • Same mechanism and user experiences with image management Multi Deployments • Docker Compose • BOSH/Pivotal Tile • Helm Chart Label • Label in project features harbor should provide? Q2: How does the Harbor architecture evolve? Q3: How to converge management of image and chart? Q4: Is it reasonable to involve day0 operation in Harbor? Website ： https://github

LiveSync, Debugging, Starter Kits o Plugins Management o Visual Studio Integration Coming o Public Beta Now! WHY: Easier bootstrapping, no SDK management, Easy debugging WHO: Windows developers, Visua

boundary.Memory model https://gchandbook.org/ Garbage collection is really “automatic memory management”. - Reference counted - C++ – std::shared_ptr - Python - Objective-C (manual or automatic - COM – AddRef()/Release() - Non-Reference counted - .NET - JVM - JavaScript Manual memory management is rarely advocated for anymore.Memory model – Manual Memory is allocated and deallocated directly

Golang specifics • Software engineering (implement/use/best practices) • Tech leadership and/or management • Your experience building XWhere to find us? Email: lukasz@lukaszgut.com, jakubdal@gmail.com