(OpenSource, event etc.); Developer, engineer, lead lost & found || Grab coffee/beer/food; 3. Hedged requests in Go - Oleg Kovalov 4. Afterparty, slowly moving to a place close byJoin Slido for Q&ALooking

ool low_latency; extern unifex::static_thread_pool workers; ex::sender auto accept_and_process_requests() { return ex::on(low_latency.get_scheduler(), accept_request()) | ex::transfer(workers { process_request(request); }) | unifex::repeat_effect(); } Accept requests on low-latency threads. Process the requests on the worker threads.16 EXAMPLE: TRANSITIONING EXECUTION CONTEXT namespace low_latency; extern unifex::static_thread_pool workers; unifex::task accept_and_process_requests() { while (true) { auto request = co_await ex::on(low_latency.get_scheduler(), accept_request());

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 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 Node1 Node2 Kube-scheduler Pod replicas CronHPA scale up How to solve the problem of improper resource requests Node Resource Oversold Node resource requests are full, but the actual load is not high. Node Allocatable Resource Allocated

Code: linear history, few feature branches • Issues: cxx20, LWG, bug, performance, etc. • Pull Requests: Used for all development • Continuous Integration: Azure Pipelines • Code format validation: issues affect binary compatibility • Will start vNext after finishing C++2031 cxx20 Issues32 Pull Requests • GH-724 Fix boyer_moore_searcher • Fixed a 43-year-old bug by implementing a 40-year-old fix up later • New process: Merge PR, add Changelog entry immediately • Advice for Reviewing Pull Requests • MSVC STL Contributors Meeting Notes • Macro _MSVC_STL_UPDATE • Updated every month by new contributors

Integration system scales greatly Aware of issues in 10 to 30 min per app Heavily testing on pull requests Numbers > 10 real test devices > 15 build machines (10 OS X, 4 Linux, 3 Windows) > 2000 tests

a multi-threaded, work-stealing scheduler. Applications can process hundreds of thousands of requests per second with minimal overhead. Fast async/await reduces the complexity of writing asynchronous

spec: accessModes: - ReadWriteOnce resources: requests: storage: 2Gi configuration: Версии ClickHouse – podTemplate apiVersion: "clickhouse

condition_variable_any  std::stop_source  Used to request a thread to stop execution  Stop requests are visible to all associated stop_sources and stop_tokens  std::stop_callback  Callback is