asynchronous-programming
Here are 397 public repositories matching this topic...
CE have released their own take on tracing, with following notable changes compared to original ZIO Tracing:
- Instead of parsing lambdas, CE throws exceptions in IO constructors and cleans up stacktraces. That also means there is no regional control of tracing and AFAIK no way to avoid slight overhead even when tracing is completely disabled – but OTOH it may probably work on Scala.js
- Trace
-
Updated
Nov 24, 2020 - Swift
-
Updated
Nov 13, 2020 - Rust
-
Updated
Nov 22, 2020 - C++
-
Updated
Nov 7, 2019 - Swift
-
Updated
Dec 3, 2020 - Python
-
Updated
Nov 23, 2020 - JavaScript
-
Updated
Nov 4, 2020 - C#
-
Updated
Nov 27, 2020 - Java
-
Updated
Nov 3, 2020 - Clojure
-
Updated
Oct 29, 2020 - Python
-
Updated
Nov 20, 2020 - C++
-
Updated
Feb 18, 2020 - C#
-
Updated
Aug 9, 2020 - Scala
-
Updated
Nov 1, 2020 - Java
-
Updated
Nov 1, 2019 - JavaScript
-
Updated
Sep 30, 2020 - Dart
-
Updated
Nov 27, 2020 - Nim
-
Updated
Dec 4, 2020 - PHP
-
Updated
Nov 14, 2020 - C++
-
Updated
Jun 24, 2020 - C
-
Updated
Sep 17, 2019 - Python
-
Updated
Dec 4, 2020 - C++
-
Updated
Oct 13, 2020 - Java
-
Updated
Mar 1, 2018 - Python
-
Updated
Jun 22, 2019 - Apex
-
Updated
Oct 17, 2019 - Pascal
-
Updated
Nov 1, 2020 - JavaScript
-
Updated
Jun 26, 2019 - Kotlin
Improve this page
Add a description, image, and links to the asynchronous-programming topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the asynchronous-programming topic, visit your repo's landing page and select "manage topics."
Hey, I recently benchmarked using jemalloc on my NUMA servers, and the difference was quite large.
Using the system allocator I got 710k req/s, while with jemalloc I got 830k req/s. That's 17% faster just by dynamically linking with a library.
Anyone else tried this?