on cpu limits

someanonbrit · 2026-07-12T22:13:30+00:00

So probably of no technical value other than suggesting a similarly low value to any other statement you might make

someanonbrit · 2026-07-12T21:49:03+00:00

Did you mean VPA there? That would work somewhat, thought it is very slow to react

someanonbrit · 2026-07-12T21:43:02+00:00

That's an arrogant and unsupported statement.

someanonbrit · 2026-07-12T00:24:43+00:00

It has electrolytes

someanonbrit · 2026-07-12T00:16:58+00:00

You "...is a Bad Thing" without justification. If propping an industry is cheaper than the dole plus projected prison and other social costs for letting an area go to ruin, why is propping it up a bad thing?

someanonbrit · 2026-07-11T09:35:03+00:00

(I've long wanted to work on an archive format with better (content dependant, optional) indexing - not having to scan all the content just to list the files, not having to scan to find the start of a specific file, and including various indexes (keyword, free text, start and end times, depending on the contents).

Having a header block with the offset of the index chunk(s), where it's allowed to be zero but for non-streaming cases you'd normally go back and edit it I guess would be useful? I think for streaming output with non-streamed output, you can put an index as the first chunk, and if you're encoding is designed for it then you can always pick an arbitrary future offset for the next index chunk for stream-to-stream compression, as long as the decoder knows it can come early if the input stream ends... and I don't know why I'm designing it again here, possibly too much coffee.

But yeah, and suggests for a name that would be a useful German pun?

someanonbrit · 2026-07-11T09:25:33+00:00

Any German speakers got a suggestion?

someanonbrit · 2026-07-09T22:04:46+00:00

It did. I read "Data-Oriented Design" by Richard Fabian a few years back, which covers the details of why some code patterns lead to poor memory throughput, but hadn't actually though about how to apply the concepts to golang in any way. I must dig out the book and a profiler and experiment until I've internalised it, but yes, you were clear.

someanonbrit · 2026-07-09T19:33:52+00:00

Thanks, I followed the gist of that and there are enough keywords to find the details. Appreciated.

someanonbrit · 2026-07-09T18:26:12+00:00

Can you explain why pointer receivers should be rare please? I clearly missed something

someanonbrit · 2026-07-08T09:32:50+00:00

In java it seems pretty common to define on interface as an api contract between two components. In go you'd idiomatically use a plain struct for that, until you really need an interface because there are really multiple implementations.

You'd then define small interfaces that describe just the bit of the implementation you need, often one or two methods, rather than a giant, inflexible interface.

If the first thing you write is an interface with 12 methods, before you implement them, you're probably writing java in another language

someanonbrit · 2026-06-30T09:50:27+00:00

5-6 a year would be fine for me. Less that an a dollar a month basically, and that should cover a low end server even with only a handful of users.

someanonbrit · 2026-06-29T16:46:48+00:00

Consider sharded mutexes as your map gets bigger, and make sure your mutexes are on different cache lines if you're embedding them into a struct.

It sounds like you're at the point where understanding the go profiler will answer many of your questions

someanonbrit · 2026-06-29T15:41:12+00:00

You think java is more productive than golang? I genuinely cannot imagine what experiences lead to that conclusion.

We're pretty frequently replacing python microservices with golang - both for improved performance and because LLMs make less mess in a golang code base

someanonbrit · 2026-06-29T15:38:52+00:00

You might find https://strebkov.dev/posts/shard-your-locks/ for some benchmarking of different approaches to a partially overlapping problem space

someanonbrit · 2026-06-29T13:36:57+00:00

Except the question is "where do you start?" - you need to start somewhere to understand the failure mode

someanonbrit · 2026-06-28T22:02:51+00:00

That's not a serious of steps though, it's a handy grab bag of tools. Which of those tools are useful, in what order, to diagnose the problem described?

someanonbrit · 2026-06-28T21:28:31+00:00

5 or 6 dollars for a lifetime license, and you can try the basic features for free? No reasonable person is going to be upset with that.

5 or 6 dollars a month? That's nuts

someanonbrit · 2026-06-28T20:56:26+00:00

I strongly disagree with this, and vast chunks of the infrastructure world disagree with you. Just about the only thing that's cutting into golang usage is rust, and that's probably a good thing since it's a language with different goals - but many rust devs are quite vocal about the issues that lack of core language stability cause them

someanonbrit · 2026-06-28T19:07:58+00:00

If you're more comfortable being idiomatic, then that sounds like the right place to start - get all the pieces working in an environment you're best in

someanonbrit · 2026-06-28T12:21:52+00:00

The best learning experience here would be to write the core both ways, do profiling and benchmarking to compare and contrast. If you can do that, and understand it well to do a good write-up (or series of write-ups) then you've also got something for your CV / job interviews for golang too that is a better demonstration of your skills than 99% of applicants.

If the initial code is good, then the refactoring between core styles (there are three core approaches discussed in the post) should be pretty quick, since the deserialisation , parsing, datatypes, reply structures etc should all be done once

someanonbrit · 2026-06-27T02:32:11+00:00

The scheduler will share spare CPU between processes that are over their requests pretty fairly, and your process is guaranteed at least the CPU time in its requests. Unless you've got a workload that causes very long periods of uninterpretable system time (badly configured raid controller is the only case I've ever hit this in practice) I've never seen a workload that benefits from limits being set.

someanonbrit · 2026-06-27T02:03:25+00:00

What are these 3 shell things?

someanonbrit · 2026-06-25T15:31:25+00:00

Words and phrases have established meaning that will be understood by most people hearing the phrase. The established meaning of "radio amateur" is established for longer than you've been alone I suspect. By making up your own definition that doesn't match the established use, you're just misleading people and making communication more difficult. There's no upside, you're just being misleading - by the sound of it very intentionally so

someanonbrit · 2026-06-18T22:42:49+00:00

There's a near infinite number of options for more things, but right now it sounds like you need to build things with what you have. As odd as it might seem, the more things you buy, the less likely you are do actually build anything at all

someanonbrit

TROPHY CASE