Designing an ultra low-overhead multithreading runtime for Nim Mamy Ratsimbazafy mamy@numforge.co Weave https://github.com/mratsim/weave Hello! I am Mamy Ratsimbazafy During the day blockchain/Ethereum Public deques are constrained by push/pop/steal/steal-half - Steal requests are implicit and have very low-overhead - Thieves can check if a victim deque is empty - They don’t work in a distributed setting eads_tasks_allocation_NUMA.md - Runtimes, NUMA, CPU+GPU computing, distributed computing 36 Designing an ultra low-overhead multithreading runtime for Nim Mamy Ratsimbazafy mamy@numforge.co Weave https://github

Leveraging C++20/23 Features for Low Level InteractionsOverview In a baremetal environment, we’re going to demonstrate e�ective use of C++ How did we end up with C language HW interactions? What are best cleaner, safer, and more testable?Why is C so proli�c? It’s the kernel, silly! 30 years ago, all low level interaction was done with C Organizations are very comfortable with C in embedded applications

● Michael A Maniscalco ○ Software Architect and Principal Developer at Lime Trading ○ We develop low latency market data and trading software for use in HFT ● Personal ○ github.com/buildingcpp ■ Work = hash_task<64>; // duration = approx 1.1µs using low_contention_task = hash_task<256>; // duration = approx 4.2µs void bench() { bench<low_contention_task>(); bench(); = hash_task<64>; // duration = approx 1.1µs using low_contention_task = hash_task<256>; // duration = approx 4.2µs void bench() { bench<low_contention_task>(); bench();

| CONFIDENTIAL Leveraging Istio for Creating API Tests Low Effort API Testing for Microservices | CONFIDENTIAL • What has changed? – Migration to microservices triggering need for extensive testing earlier Create and maintain a balanced test pyramid Create different types of tests with low effort 7 What we need… End-to-end Component Service | CONFIDENTIAL REQUEST RESPONSE API MOCKS

26dacdde40968a37ba9eaa864d40e45051ec5448 Finding Breakdown Critical issues 0 High issues 4 Medium issues 5 Low issues 7 Informational issues 2 Total issues 18 Category Breakdown Access Controls 7 Configuration 2 Component Breakdown Istio 10 Istio Sidecar 3 Istioctl 2 Pilot 3 Key Critical High Medium Low Informational 3 | Google Istio Security Assessment Google / NCC Group Confidential Table of Findings Sidecar Image Not Hardened 001 Low The Sidecar Does Not Use Apparmor/Seccomp By Default 005 Low Insecure File Permissions Set 007 Low Istio Client-Side Bypasses 014 Low Sidecar Envoy Administrative

auto-registration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549 3 Low-level discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended item value preprocessing JavaScript It is now possible to apply preprocessing to item value or low-level discovery values using JavaScript. The JavaScript step accepts one parameter - a non-empty JavaScript steps. Preprocessing support on Zabbix proxy For hosts monitored by proxies, all item (including low-level discovery rules, dependent items) value preprocessing will now be done on the proxy. Given

autoregistration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715 3 Low-level discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . gather some data. In the new version it is possible to test the item (template item, item prototype, low-level discovery rule) from the user interface even before saving and, if configured correctly, get is now possible to filter out items, triggers, hosts and graphs or override their attributes during low-level discovery based on LLD object and prototype name. IPMI sensor discovery A new ipmi.get IPMI

autoregistration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670 3 Low-level discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . is not available Host prototypes Two new options can now be set on a host prototype level, making low-level discovery even more flexible. Custom interfaces Host prototype configuration form now allows values. Values of these macros should be entered manually.” SNMP items can be tested as an item, a low-level discovery rule and an item prototype. All these entities can be tested on template level as

autoregistration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601 3 Low-level discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . new item may also be used for low-level discovery using ODBC SQL queries. Compared to the db.odbc.discovery[] item from previous versions, this item does not define low-level discovery macros in the with JSONPath to point to the required values in the returned JSON. Low-level discovery Low-level discovery of block devices Low-level discovery of block devices and their type is supported using a new