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

Gopher  China  2015  Resource  Scheduling  &  Container  Technology  for  Financial  Service  动态资源管理和容器技术  在金融行业的架构探索和明天  余军  Gopher  China  2015  Gopher  China  2015  China  2015  求解之路的探索  n 他们是否解决了我们的问题?  n No   ① Mesos  采用了DRF(Dominant  Resource  Fairness)  调度机制。 YARN自带FIFO、Capacity  Scheduler和Fair  Scheduler(借鉴了 Mesos的DRF)。  ② Mes oop中Capacity  Scheduler的调度机制，将所有资源分成若干个queue，每个 queue分配一定量的资源，每个user有一定的资源使用上限。  ③ Mesos采用了Resource  Offer机制，这种调度机制面临着资源碎 片问题，即：每个节点上的资源不可能全部被分配完，剩下的一 点可能不足以让任何任务运行，这样，便产生了类似于操作系统 中的内存碎片问题。 

that take a user-suppiled lambda to generate the data needed to render our desired compile-time resource! These are e�ectively templated functions, but we will use the cleaner auto parameter syntax for

effective. Routes based on URI templates RFC REST-inspired mapping of URIs to resources Global, resource, and method hooks Idiomatic HTTP error responses Full Unicode support Intuitive request and response API Class Req/Resp Cookies Status Codes Error Handling Redirection Middleware Components Hooks Routing Utilities Testing Changelogs 1.0.0 0.3.0 0.2.0 Created using Sphinx 1.3.5. index modules | next authorize the request, taking into account the user’s role and the requested resource. Why doesn’t Falcon create a new Resource instance for every request? Falcon generally tries to minimize the number

effective. Routes based on URI templates RFC REST-inspired mapping of URIs to resources Global, resource, and method hooks Idiomatic HTTP error responses Full Unicode support Intuitive request and response Class Request & Response Cookies Status Codes Error Handling Media Redirection Middleware Hooks Routing Utilities Testing Community Guide Get Help Contribute to Falcon FAQ Changelogs 1.4.1 1.4.0 1 tests Serving Images Introducing Hooks Error Handling What Now? FAQ Design Philosophy Performance Routing Extensibility Request Handling Response Handling Misc. Introduction Perfection is finally attained

effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks • Idiomatic HTTP error responses • Full Unicode support • Intuitive request deployments. Features • Highly-optimized, extensible code base • Intuitive routing via URI templates and REST-inspired resource classes • Easy access to headers and bodies through request and response process_response(self, req, resp, resource): if 'result' not in resp.context: return resp.body = json.dumps(resp.context['result']) def max_body(limit): def hook(req, resp, resource, params): length = req.content_length

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 5.4.13 Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 5 reliance on magic globals for routing and state management • Stable interfaces with an emphasis on backwards-compatibility • Simple API modeling through centralized RESTful routing • Highly-optimized, extensible reliance on magic globals for routing and state management • Stable interfaces with an emphasis on backwards-compatibility • Simple API modeling through centralized RESTful routing • Highly-optimized, extensible

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 5.4.13 Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 5 reliance on magic globals for routing and state management • Stable interfaces with an emphasis on backwards-compatibility • Simple API modeling through centralized RESTful routing • Highly-optimized, extensible reliance on magic globals for routing and state management • Stable interfaces with an emphasis on backwards-compatibility • Simple API modeling through centralized RESTful routing • Highly-optimized, extensible

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242 5.4.13 Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 5 effective. • Routes based on URI templates RFC • REST-inspired mapping of URIs to resources • Global, resource, and method hooks • Idiomatic HTTP error responses • Full Unicode support • Intuitive request Highly-optimized, extensible code base • Intuitive routing via URI templates and REST-inspired resource classes • No reliance on magic globals for routing and state management • Easy access to headers and