Hacker News — vinext + Cloudflare Workers

new
past
show
ask
show
jobs
submit

▲Cactus, a work-stealing parallel recursion runtime for C (github.comself.__VINEXT_RSC_CHUNKS__=self.__VINEXT_RSC_CHUNKS__||[];self.__VINEXT_RSC_CHUNKS__.push("2:I[\"aadde9aaef29\",[],\"default\",1]\n3:I[\"6e873226e03b\",[],\"Children\",1]\n5:I[\"bc2946a341c8\",[],\"LayoutSegmentProvider\",1]\n6:I[\"6e873226e03b\",[],\"Slot\",1]\n7:I[\"3506b3d116f7\",[],\"ErrorBoundary\",1]\n8:I[\"a9bbde40cf2d\",[],\"default\",1]\n9:I[\"3506b3d116f7\",[],\"NotFoundBoundary\",1]\na:\"$Sreact.suspense\"\n:HL[\"/assets/index-BLEkI_5r.css\",\"style\"]\n")>)

14 points by enduku 4 days ago | 2 comments

Neywiny 3 days ago [-]

If other threads can pull out of the dequeue, is there an advantage to not just having one common dequeue for all threads?

enduku 2 days ago [-]

Yes: contention and locality.

In Cactus the fast path is local. A worker pushes its own continuation onto its own deque, runs the child, and later tries to reclaim that continuation locally. Other workers only touch that deque when they become idle and steal.

With one global deque, every fork/pop/steal hits the same shared structure, making it a cache-coherency hotspot.

Per-worker deques make the common case mostly uncontended; stealing is only the load-balancing fallback.

So a global deque is simpler, but it scales worse.

stefantalpalaru 3 days ago [-]

[dead]

Rendered at 18:49:51 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.