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 multithreading: definitions and use-cases ◇ Parallel APIs ◇ Sources of overhead and runtime design ◇ Minimum viable runtime plan in a weekend 4 Understanding the design space Concurrency vs parallelism hardware threads The same distinctions can be done at a multithreaded language or multithreading runtime level. The problem 8 How to schedule M tasks on N hardware threads? Latency vs Throughput

Go runtime related problems in TiDB production environment About me ● Arthur Mao(毛康力), Senior Engineer@PingCAP ● TiDB core developer (top3 contributor) ● GitBook about golang internals (@tiancaiamao) IO is ready => goroutine wake up == 4.3ms ○ Sometime even 10ms+ latency here! ○ The time spend on runtime schedule is not negligible ● When CPU is overload, which goroutine should be given priority? Analysis longer to be scheduled ● The runtime scheduling does not consider priority ● CPU dense workload could affect IO latency Conclusion Part II - Memory control ● Go Runtime ○ Allocated from OS (mmaped)

company. Ⓡ © 2021 Apex.AI, Inc. Igor Bogoslavskyi Testing the compilability of the code at runtime© 2021 Apex.AI, Inc. Errors have a high cost, so rigorous testing is a must We use increasingly

with full support for hot code- language with full support for hot code- reloading at runtime reloading at runtime by Viktor Kirilov 1 Me, myself and I Me, myself and I my name is Viktor Kirilov - fine-tuning values interactive (REPL-like): very useful for exploration and teaching Runtime compilation - WHY Runtime compilation - WHY 33 replacing entire functions: using shared libraries OR hot-patching: https://github.com/ddovod/jet-live http://bit.ly/runtime-compilation-alternatives cling inspector Jupiter RCRL Runtime compilation for C/C++: HOW Runtime compilation for C/C++: HOW 34 Replace "compiling"

package data files 1.3.5. Checking runtime key periodically 1.3.6. Binding to many machines 1.3.7. Using outer file to store runtime key 1.3.8. Localization runtime error 1.3.9. Packing obfuscated scripts 4.7. Internationalization runtime error message 1.4.8. Generating cross platform scripts 1.4.9. Obfuscating scripts for multiple Python versions 1.4.10. Using shared runtime package 1.5. Customization Customization and Extension 1.5.1. Changing runtime package name 1.5.2. Appending assert functions and modules 1.5.3. Using plugin to fix loading issue in darwin 1.5.4. Using hook to bind script to docker id 1.5

object to protect constants and literal strings. Obfuscate co_code of each function (code object) in runtime. Clear f_locals of frame as soon as code object completed execution. Verify the license file of obfuscated PyUpdater Binding obfuscated scripts to Python interpreter Customizing cross protection code Storing runtime file license.lic to any location Register multiple pyarmor in same machine How to get license information config build info check banchmark register download runtime Understanding Obfuscated Scripts Global Capsule Obfuscated Scripts Bootstrap Code Runtime Package The License File for Obfuscated Script Key

object to protect constants and literal strings. Obfuscate co_code of each function (code object) in runtime. Clear f_locals of frame as soon as code object completed execution. Verify the license file of obfuscated PyUpdater Binding obfuscated scripts to Python interpreter Customizing cross protection code Storing runtime file license.lic to any location Register multiple pyarmor in same machine How to get license information config build info check banchmark register download runtime Understanding Obfuscated Scripts Global Capsule Obfuscated Scripts Bootstrap Code Runtime Package The License File for Obfuscated Script Key

code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 i 3.22 Storing runtime file license.lic to any location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 6.14 runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 7.4 Runtime Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2023 Threat model Dapr is a framework for building cloud-native applications. It consists of a runtime and a set of building blocks that allow users to move infrastructure-related tasks out of their applications multiple microservices. Illustrated high-level overview Having outlined the main parts of Dapr, the runtime and the components, we can look at a high-level view of Dapr: 6 Dapr security audit 2023 At the in github.com/dapr/dapr/cmd/daprd2. We now do a quick code walk through of how Dapr starts the runtime and sets up the HTTP and gRPC endpoints and the components. The purpose of this brief section is

protection code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 3.21 Storing runtime file license.lic to any location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 6.14 runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 7.4 Runtime Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .