frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Hurried Announcement: Alessandro Masullo GRH

https://math216.wordpress.com/2026/11/20/hurried-announcement-alessandro-masullo-grh/
1219•jasondavies•4h ago•568 comments

Inkling 2 Mini

https://thinkingmachines.ai/news/inkling-2-mini/
450•jasondavies•2h ago•67 comments

Levent Alpöge claims proof of the Generalized Riemann Hypothesis [pdf]

https://alpo.ge/remark.pdf
2208•iamronaldo•8h ago•1508 comments

We promoted developers into architects without informing them

https://manidoraisamy.com/developer-to-architect.html
219•QueensGambit•4h ago•130 comments

Unforced Navier-Stokes Singularity and the Generalized Riemann Hypothesis

https://terrytao.wordpress.com/2026/11/20/unforced-euler-singularity-unforced-navier-stokes-singu...
274•archon1410•5h ago•88 comments

Language Models Can Rewrite Their Own Weights

https://arxiv.org/abs/2611.21885
308•lwhsiao•6h ago•101 comments

The stochastic parrots have apparently proved the Riemann Hypothesis

https://scottaaronson.blog/?p=10344
149•stratos123•2h ago•108 comments

A few hours ago Google DeepMind created a math horizon repo

https://github.com/google-deepmind/math-horizon
25•RubenLtke•1h ago•5 comments

Vibecoding an inference chip

https://ankitg.me/blog/vibecoding-inference-chip/
90•ankitvgupta•4h ago•28 comments

Finite-time blow-up for the Navier–Stokes equations

https://github.com/tristanbuckmaster/navier-stokes/
235•trotro•7h ago•76 comments

DreamCoder: Coding harness and IDE from the author of Mastering Emacs

https://www.masteringemacs.org/article/announcing-dreamcoder
47•facundo_olano•2h ago•6 comments

And Yet, It Moves

https://signoregalilei.com/2026/11/20/and-yet-it-moves/
44•notfried•2h ago•22 comments

If you can't explain something in simple terms, you don't understand it (2017)

https://kottke.org/17/06/if-you-cant-explain-something-in-simple-terms-you-dont-understand-it
590•sammatilda•13h ago•281 comments

Winedroid – run Android apps without Android (WASM demo)

https://winedroid.soham.sh/demo/
69•sohzm•3h ago•25 comments

Microsoft announces Windows Server 2028 with hardened security

https://www.bleepingcomputer.com/news/microsoft/microsoft-announces-windows-server-2028-with-hard...
53•N19PEDL2•2d ago•50 comments

Signal Is Serious About Protecting Your Privacy

https://signal.org/blog/protecting-your-privacy/
453•dotcoma•13h ago•283 comments

Frostbite: A new CPU architecture discovered, designed and verified by AI

https://architectlabs.com/blog/frostbite
596•shioyama•12h ago•315 comments

Nvidia accounting under SEC investigation, sources say

https://finance.yahoo.com/markets/article/nvidia-stock-extends-25-trillion-rout-as-sec-probe-repo...
151•ftchd•2h ago•63 comments

Show HN: An API for word timestamps from speech, 75% within 20ms

https://quebec.yarn.so
46•jasperstory•3d ago•5 comments

I'm Peter Roberts, immigration attorney who does work for YC and startups. AMA

89•proberts•6h ago•119 comments

Show HN: OpenComputer – an open source alternative to Devin

https://github.com/diggerhq/opencomputer
34•iacguy•2h ago•12 comments

Show HN: I made an audio-to-MIDI model 60x more efficient

https://kobi.music/research/dettato
216•hidude562•3d ago•47 comments

Reverse Engineering my cat's litter box

https://master--ytulsiani.netlify.app/blog/furrytails/
19•allidoisvim•2h ago•7 comments

The Hungry Butler Effect: Concealed Commercial Incentives in LLMs

https://www.researchgate.net/publication/418143113_The_Hungry_Butler_Effect_Concealed_Commercial_...
3•undefinedmethod•31m ago•0 comments

Google Workers Tell Their Employer Not to Punish Schools That Don't Want AI

https://www.motherjones.com/politics/2026/11/google-alphabet-union-school-ai-protest-gemini-worke...
226•cdrnsf•5h ago•161 comments

Running two PSP emulators on one Switch 2 and sharing one via GameShare

https://github.com/XITRIX/ppsspp-nx2/blob/master/SWITCH2-GAMESHARE.md
50•khalidkhair•5h ago•0 comments

The G1 Garbage Collector

https://dev.java/learn/jvm/tool/garbage-collection/g1gc-overview/
93•ejboy•3d ago•49 comments

Floppy3.5: A portable 3.5-inch floppy WiFi NAS

https://github.com/bigcrimping/floppy3.5
131•fortran77•1d ago•55 comments

PostgreSQL 19: A hands-on tour with runnable browser examples

https://certuvia.com/blog/postgres-19
38•petrpravda•5h ago•3 comments

LZ-RDO lands in ARM's astc-encoder

https://www.jonolick.com/home/lz-rdo-lands-in-arms-astc-encoder
14•dverlaeckt80•2d ago•0 comments
Open in hackernews

Understanding the Go Scheduler

https://nghiant3223.github.io/2025/04/15/go-scheduler.html
180•gnabgib•1y ago

Comments

90s_dev•1y ago
I heard that the scheduler is a huge obstacle to many potential optimizations, is that true?
NAHWheatCracker•1y ago
In some ways, yes. If you want to optimize at that level you ought to use another language.

I'm not a low level optimization guy, but I've had occasions where I wanted control over which threads my goroutines are running on or prioritizing important goroutines. It's a trade off for making things less complex, which is standard for Go.

I suppose there's always hope that the Go developers can change things.

silisili•1y ago
You can kinda work around this though. runtime package has a LockOSThread that pins a goroutine to its current thread and prevents others from using it.

If you model it in a way where you have one goroutine per os thread that receives and does work, it gets you close. But in many cases that means rearching the entire code base, as it's not a style I typically reach for.

naikrovek•1y ago
That sounds a lot like just using another language.
silisili•1y ago
It's really not that bad. If you have a codebase in Go you can speed up, it's fine.

That said, if you're greenfielding and see this as a limitation to begin with, picking another language is probably the right way.

jerf•1y ago
If you need it here or there, no. I've got a use case where I need a single locked thread for a particular syscall's functionality. It's not like it leaks out into the rest of the program and everything else has to change to accomodate it.

If you need it pervasively, Go may not be the correct choice. Then again, the list of languages that is not a correct choice in that case is quite long. That's a minority case. An important one, but a minority one.

jasonthorsness•1y ago
It's always a sign of good design when something as complex as the scheduler described "just works" with the simple abstraction of the goroutine. What a great article.

"1/61 of the time, check the global run queue." Stuff like this is a little odd; I would have thought this would be a variable dependent on the number of physical cores.

01HNNWZ0MV43FF•1y ago
That's so funny. I just saw `61` in the Tokio code with a comment "copied this from Go"
__turbobrew__•1y ago
Make sure you set GOMAXPROCS when the runtime is cgroup limited.

I once profiled a slow go program running on a node with 168 cores, but cpu.max was 2 cores for the cgroup. The runtime defaults to set GOMAXPROCS to the number of visible cores which was 168 in this case. Over half the runtime was the scheduler bouncing goroutines between 168 processes despite cpu.max being 2 CPU.

The JRE is smart enough to figure out if it is running in a resource limited cgroup and make sane decisions based upon that, but golang has no such thing.

xyzzy_plugh•1y ago
Relevant proposal to make GOMAXPROCS cgroup-aware: https://github.com/golang/go/issues/73193
robinhoodexe•1y ago
Looks like it was just merged btw.
yencabulator•1y ago
This should be automatic these days (for the basic scenarios).

https://github.com/golang/go/blob/a1a151496503cafa5e4c672e0e...

jasonthorsness•1y ago
uh isn't that change 3 hours old?
kortex•1y ago
Fantastic writeup! Visualizations are great, the writeup is thorough but readable.
weiwenhao•1y ago
Your write-up is so detailed that I even feel like I could implement a complete golang scheduler myself
davidw•1y ago
I'd be interested in seeing a comparison of this and the BEAM/Erlang/Elixir scheduler by someone paying attention to the details.
yencabulator
•
1y ago
Oh heh yes it is. I just remembered the original discussion from 2019 (https://github.com/golang/go/issues/33803) and grepped the source tree for cgroup to see if that got done or not, but didn't check when it got done.

As said in 2019, import https://github.com/uber-go/automaxprocs to get the functionality ASAP.

jasonthorsness•1y ago
super-weird coincidence but welcome, I have been waiting for this for a long time!
williamdclt•1y ago
I honestly can’t count on my fingers and toes how many times something very precisely relevant to me was brought up or sorted out hours-to-days before I looked it up. And more often than once, by people I personally knew!

Always a weird feeling, it’s a small world

formerly_proven•1y ago
This is probably going to save quadrillions of CPU cycles by making an untold number of deployed Go applications a bit more CPU efficient. Since Go is the "lingua franca" of containers, many ops people assume the Go runtime is container-aware - it's not (well not in any released version, yet).

If they'd now also make the GC respect memory cgroup limits (i.e. automatic GOMEMLIMIT), we'd probably be freeing up a couple petabytes of memory across the globe.

Java has been doing these things for a while, even OpenJDK 8 has had those patches since probably before covid.

mappu•1y ago
GOMEMLIMIT is not as easy, you may have other processes in the same container/cgroup also using memory.
kunley•1y ago
As long as I admit respecting cgroup's setting is a good thing, I am not sure it's really quadrillions.

Or is it? Need calculations

formerly_proven•1y ago
I would've expected it to be either way too much or way too little, but after doing the math it could be sorta in the right ballpark, at least cosmically speaking.

Let's go with three quadrillion (which is apparently 10^15), let's assume a server CPU does 3 GHz (10^9), that's 10^6, a day is about 100k seconds, so ~ten days. But of course we're only saving cycles. I've seen throughput increase by about 50% when setting GOMAXPROCS on bigger machines, but in most of those cases we're looking at containers with fractional cores. On the other hand, there are many containers. So...

kunley•1y ago
Nice reasoning, thanks.

Hey, but what did you have in mind with regard to bigger machines? I think we're talking here about lowering GOMAXPROCS to have in effect less context switching of the OS threads. While it can bring some good result, a gut feeling is that it'd be hardly 50% faster overall, is your scenario the same then?

01HNNWZ0MV43FF•1y ago
Trying to see if Rust and Tokio have the same problem. I don't know enough about cgroups to be sure. Tokio at this line [1] ends up delegating to `std::thread::available_parallelism` [2] which says

> It may overcount the amount of parallelism available when limited by a process-wide affinity mask or cgroup quotas and sched_getaffinity() or cgroup fs can’t be queried, e.g. due to sandboxing.

[1] https://docs.rs/tokio/1.45.0/src/tokio/loom/std/mod.rs.html#...

[2] https://doc.rust-lang.org/stable/std/thread/fn.available_par...

nvarsj•1y ago
Probably not?

The fundamental issue comes down to background GC and CPU quotas in cgroups.

If your number of worker threads is too high, GC will eat up all the quota.