Login

r/DistributedComputing

Walks the full cmd/compile pipeline in order: package names, data structures, and the SSA construction that drives inlining, escape analysis, bounds-check elimination, and register allocation, with flags to observe each phase directly.
▲ 232 r/DistributedComputing+19 crossposts

Walks the full cmd/compile pipeline in order: package names, data structures, and the SSA construction that drives inlining, escape analysis, bounds-check elimination, and register allocation, with flags to observe each phase directly.

This one took a while, it's probably the longest thing I've written on this blog. I wanted to do a proper end-to-end walkthrough of cmd/compile: real package names, real data structures, diagrams for the AST and SSA CFG, and the flags you actually need (-m, -m=2, GOSSAFUNC, -S) to observe each phase yourself rather than just take my word for it.

Covers the full pipeline: lexer → parser → type checker → IR lowering → SSA construction → optimization passes (inlining, escape analysis, BCE, nil check elimination, register allocation) → architecture-specific code emission.

Hope it's useful — happy to answer questions or push back on anything that looks wrong.

blog.gaborkoos.com
u/OtherwisePush6424 — 9 days ago
▲ 39 r/DistributedComputing+4 crossposts

I'm building a C++ code generator that helps build distributed systems. It's implemented as a 3-tier system. The back and middle tiers only run on Linux. The front tier is portable. It's free to use; there aren't any trial periods or paid plans.

This past Tuesday another jewelry store was robbed by a bunch of thugs. I saw some of this trouble brewing back in the 1990s and realized SaaS was a gift from above in terms of dealing with corruption. I'm glad I have some open-source code for my portfolio, but I'm glad it's not all I have.

There was another robbery in Freemont, California in June of 2025. Around 24 thieves raided a jewelry store and stole over 1.7 million$ of jewelry in 70 seconds. If the stewards of that store decide to rebuild, I predict they won't replace the display cases that were smashed. It will be a "by appointment only" store and they will frisk you before they show you anything. Of the 24 thieves, only a handful of them have been caught.

In other words, the store managers will replace their open model with a SaaS model. And who can blame them?

u/Middlewarian — 9 days ago
▲ 7 r/DistributedComputing+2 crossposts

Looking for help testing lettuce.

On last fireside Jring-o spoke about needing testers for new distributive computing platform lettuce. I’m probably the lest tech savy person in this group, but with help, I was able to set it up. It’s currently configured to need 3 separate computers to verify one work unit. I was looking for someone (more specifically with an Nvidia gpu) to validate my work units. The is a “lettuce testing” thread on the Gridcoin discord. Below are links to the site project, Git, and discord. I figure a vast majority of us are science nerds and we can knock out this testing to hopefully, at some point, get this on the whitelist. Lettuce is basically an easier to set up BOINC. This will get us involved closer with researchers. Anyway, come validate my work units. (Note: there are also CPU only projects.)

Git/download: https://github.com/jring-o/lettuce-compute

Project: https://compute.scios.tech/leafs

Discord testing: https://discord.com/channels/211637812968161280/1517249245596614686

u/UrafuckinNerd — 9 days ago
▲ 6 r/DistributedComputing+1 crossposts

186 database records. 187 Kafka events. Where would you look first?

I’ve been experimenting with turning distributed-systems failure modes into fictional incident investigations.

In this one, a lab registers 186 samples. Registration succeeds in the database, then publishes label-print commands to Kafka.

Later the team discovers 187 print events.

Eventually they reconstruct the sequence:

DB commit succeeds → Kafka publish succeeds → ACK is lost → application retries → duplicate print command → duplicate physical label → subsequent labels shift by one.

I used producer idempotence + business-level deduplication on label ID as part of the remediation, with a scanner guardrail at the physical boundary.

Architecture question: Would you consider that sufficient, or would you redesign the DB→Kafka boundary around an outbox/CDC approach?

reddit.com
u/Glittering-Click-48 — 12 days ago