Understanding Rust Thread Safety
Programming interviews can be a great learning experience for interviewers as well as interviewees. In fact, I recently had the opportunity to learn something new about Rust while interviewing an engineering candidate. Background About our Interview ProcessAt OneSignal, we don't believe in handing someone a problem and watching them flounder with zero autocomplete and zero docs. Engineers who appl
Practical libc-free threading on Linux
Suppose you’re not using a C runtime on Linux, and instead you’re programming against its system call API. It’s long-term and stable after all. Memory management and buffered I/O are easily solved, but a lot of software benefits from concurrency. It would be nice to also have thread spawning capability. This article will demonstrate a simple, practical, and robust approach to spawning and managing
Optimize long tasks  | Articles  | web.dev
Published: September 30, 2022, Last updated: December 19, 2024 Common advice for keeping JavaScript apps fast tends to boil down to the following advice: "Don't block the main thread." "Break up your long tasks." This is great advice, but what work does it involve? Shipping less JavaScript is good, but does that automatically equate to more responsive user interfaces? Maybe, but maybe not. To unde
Choose the Right Python Concurrency API - Super Fast Python
How to Choose the Right Python Concurrency API Python standard library offers 3 concurrency APIs. How do you know which API to use in your project? In this tutorial, you will discover a helpful step-by-step procedure and helpful questions to guide you to the most appropriate concurrency API. After reading this guide, you will also know how to choose the right Python concurrency API for current and
詳解 Linux ãƒãƒƒãƒˆãƒ¯ãƒ¼ã‚¯ - NAPI ç·¨ (後編) - VA Linux エンジニアブãƒã‚°
1. ã¯ã˜ã‚ã« 2. Busy Poll Socket 2.1 æ¦‚è¦ 2.2 使ã„æ–¹ 2.3 内部実装 3. kthread NAPI polling 3.1 æ¦‚è¦ 3.2 使ã„æ–¹ 3.3 内部実装 4. ã¾ã¨ã‚ 執ç†è€… : 西æ‘　大助 1. ã¯ã˜ã‚ã« å‰ç·¨ã§ã¯ã€NAPI ã¨ãã‚Œã«é–¢é€£ã™ã‚‹ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢å‰²ã‚Šè¾¼ã¿ã®ä»•çµ„ã¿ã«ã¤ã„ã¦è§£èª¬ã—ã¾ã—ãŸã€‚ 本稿ã§ã¯ã€å‰å›žã®æœ€å¾Œã«è§¦ã‚ŒãŸé€šã‚Šã€Linux kernel ã«çµ„ã¿è¾¼ã¾ã‚Œã¦ã„ã‚‹ã€NIC をソフトウェア割り込ã¿ä»¥å¤–㧠polling ã™ã‚‹ãŸã‚ã®ä»•çµ„ã¿ã§ã‚ã‚‹ã€Busy Poll Socket 㨠kthread NAPI polling ã«ã¤ã„ã¦è§£èª¬ã—ã¾ã™ã€‚ 2. Busy Poll Socket 2.1 æ¦‚è¦ ä½¿ç”¨ã™ã‚‹ socket ã« setsockopt(2) システムコールを使ã„ã€@optname=SO_BUSY_POLL ã§æ™‚é–“(μ秒å˜ä½ã€‚以é™
partytown ã® Worker ã‹ã‚‰ã®åŒæœŸçš„メインスレッドæ“作を実装ã—ã¦ã¿ã‚‹
Partytown ã¨ã¯ GitHub - BuilderIO/partytown: Relocate resource intensive third-party scripts off of the main thread and into a web worker. 🎉 今PartytownãŒãƒ¤ãƒã„。JavaScript Sandboxã®æœªæ¥ã¯ã©ã£ã¡ã ？ è¦ã¯ 3rd party script を安全ã«éš”離ã™ã‚‹ãŸã‚〠WebWorker + DOM ã® mock ã§å‹•ã‹ã™ã€‚ GitHub - ampproject/worker-dom: The same DOM API and Frameworks you know, but in a Web Worker. ã“ã® DOM ãŒã™ã”ã„2018: worker-dom - mizchi's blog worker-dom ã¨ã®ä¸€ç•ªã®é•
Goroutines Are Not Significantly Smaller Than Threads
Goroutines Are Not Significantly Smaller Than Threads Mar 12, 2021 The most commonly cited drawback of OS-level threads is that they use a lot of RAM. This is not true on Linux. Let’s compare memory footprint of 10_000 Linux threads with 10_000 goroutines. We spawn 10k workers, which sleep for about 10 seconds, waking up every 10 milliseconds. Each worker is staggered by a pseudorandom delay up to
マルãƒã‚¹ãƒ¬ãƒƒãƒ‰ãƒ»ãƒ—ãƒã‚°ãƒ©ãƒŸãƒ³ã‚°ã®é“å…·ç®±
ã¾ãˆãŒã クラウド上ã®ä»®æƒ³ã‚µãƒ¼ãƒã‹ã‚‰æ‰‹å…ƒã®ã‚¹ãƒžãƒ¼ãƒˆãƒ•ã‚©ãƒ³ã¾ã§ã€ã„ã¾ã‚„複数ã®CPUコアをæ載ã™ã‚‹ãƒžãƒ«ãƒã‚³ã‚¢ã¯ã©ã“ã«ã§ã‚‚ã‚る環境ã«ãªã‚Šã¾ã—ãŸã€‚ãƒãƒ¼ãƒ‰ã‚¦ã‚§ã‚¢å´ãŒä¸¦åˆ—(Parallel)・並行(Concurrent)処ç†ã«å‘ã‘ã¦æ€¥é€Ÿã«é€²åŒ–ã™ã‚‹ä¸€æ–¹ã§ã€ã‚½ãƒ•ãƒˆã‚¦ã‚§ã‚¢å´ã¤ã¾ã‚Šãƒ—ãƒã‚°ãƒ©ãƒŸãƒ³ã‚°è¨€èªžã®é€²åŒ–ã¯ã•ã»ã©è¿½ã„付ã„ã¦ã„ã¾ã›ã‚“。並行処ç†è¨˜è¿°ã®æ‰‹è»½ã•ã‚’求ã‚㟠Go言語 ã‚„ã€ãƒžãƒ«ãƒã‚¹ãƒ¬ãƒƒãƒ‰å‡¦ç†ã®å®‰å…¨æ€§ã‚’é‡è¦–ã™ã‚‹ Rust言語 ãªã©ãŒç™»å ´ã—ã¦ã¯ã„ã‚‹ã‚‚ã®ã®ã€ã€Œæ™®é€šã«ãƒ—ãƒã‚°ãƒ©ãƒ を記述ã™ã‚‹ã ã‘ã§è¤‡æ•°CPUコア環境ã§é«˜é€Ÿã«èµ°ã‚‹ãƒ—ãƒã‚°ãƒ©ãƒŸãƒ³ã‚°è¨€èªžã€ã¯é ã„夢物語ã®ã¾ã¾ã§ã™ã€‚ モダンãªãƒ—ãƒã‚°ãƒ©ãƒŸãƒ³ã‚°è¨€èªžã‚„並列・並行処ç†ãƒ©ã‚¤ãƒ–ラリã¯ã€è¤‡é›‘ã§é›£è§£ãªãƒžãƒ«ãƒã‚¹ãƒ¬ãƒƒãƒ‰å‡¦ç†ã‚’直接記述ã—ãªãã¦ã™ã‚€ã‚ˆã†ã€å®‰å…¨æ€§ãƒ»åˆ©ä¾¿æ€§ã®é«˜ã„抽象化レイヤをæä¾›ã—ã¾ã™ï¼ˆä¾‹ï¼šGo言語ã®goroutineã¨channelã€Rust言語㮠Rayonライブラリ）。ã—
Linuxã§ã‚¹ãƒ¬ãƒƒãƒ‰ã”ã¨ã«å›ºæœ‰ã®IDを発行ã§ããªã„ã‹ - ãƒãƒ¼ãƒ•ã‚¡ã‚¤æ—¥è¨˜
ãªã‚‹ã¹ãç°¡å˜ãªãƒã‚¸ãƒƒã‚¯ã§ã€ãŠãŠã‚€ã被らãªã„よã†ãªIDをスレッドã”ã¨ã«åã‘ãªã„ã ã‚ã†ã‹ã€ãれもåŒã˜ã‚¹ãƒ¬ãƒƒãƒ‰ãªã‚‰ä½•åº¦å‘¼ã³å‡ºã—ã¦ã‚‚åŒã˜IDã«ãªã‚‹ã‚„ã¤ï¼ˆï¼ã‚ャッシュãŒè¦ã‚‰ãªã„）ã€ã¨æ€ã£ã¦ã“ã†ã„ã†ã®ã‚’考ãˆãŸã€‚ ã¨ã‚Šã‚ãˆãšã‚³ãƒ¼ãƒ‰: #define _GNU_SOURCE #include <stdio.h> #include <stdlib.h> #include <unistd.h> #include <sys/syscall.h> pid_t gettid(void) { return syscall(SYS_gettid); } unsigned long long getthreadseq(void) { pid_t tid = gettid(); char fmt[] = "/proc/self/task/%d/stat"; char statpath[sizeof(fmt)+10]; un
1
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
Cost of a thread in C++ under Linux – Daniel Lemire's blog
{{#tags}}- {{label}}
{{/tags}}