riv991

6 ms·

31.
Microsoft blames EU rules for allowing biggest IT outage to happen(telegraph.co.uk)
21 points by riv991 2y ago|28 comments
32.
Google parent in talks to buy cyber security startup Wiz for $23B(ft.com)
3 points by riv991 2y ago|0 comments
33.
Securing our software supply-chain better with reproducible builds for enclaves(monzo.com)
1 points by riv991 2y ago|0 comments
34.
Event-Driven Architectures – The Queue vs. the Log(jack-vanlightly.com)
2 points by riv991 2y ago|0 comments
35.
Virtualizing Our Storage Engine(honeycomb.io)
1 points by riv991 2y ago|0 comments
36.
by riv991 2y ago
You can argue the complete opposite point with Novo Nordisk. It's up to the foundation to use it's influence
37.
by riv991 2y ago
The foundation still owns the vast majority of the company
38.
PGHero: A Performance Dashboard for Postgres(github.com)
4 points by riv991 2y ago|0 comments
39.
Benchmarking PostgreSQL Connection Poolers: PgBouncer, PgCat and Supavisor(tembo.io)
17 points by riv991 2y ago|0 comments
40.
by riv991 3y ago
The eBPF website has a list of projects using it, that can give you a decent flavour of what people use it for. https://ebpf.io/applications/
41.
by riv991 3y ago
I really hope Intel succeed here, not because I'm a massive Intel fan, but we need some competition
42.
by riv991 3y ago
So sad seeing nuclear energy falling despite all the other good news
43.
BPF Memory Forensics with Volatility 3(lolcads.github.io)
1 points by riv991 3y ago|0 comments
44.
4B If Statements(andreasjhkarlsson.github.io)
6 points by riv991 3y ago|1 comments
45.
by riv991 3y ago
Tidal energy is not renewable! We'd be tidally locked to the moon in 1000 years if we used Tidal for 1% of our energy consumption. https://cs.stanford.edu/people/zjl/pdf/tide.pdf
46.
by riv991 3y ago
Great to see Microsoft deploying some of it's capital to develop SMRs, the potential seems great, but governments don't seem to have gone further than nuclear submarines.
47.
by riv991 3y ago
It was, they talk about it here: https://sre.google/sre-book/service-level-objectives/
48.
by riv991 3y ago
They wrote a pretty interesting blog about the rewrite. https://github.blog/2023-02-06-the-technology-behind-githubs...
49.
Exploring a Postgres Query Plan(notes.eatonphil.com)
7 points by riv991 3y ago|0 comments
50.
by riv991 3y ago
Incredible how you can see CS7 extending from Elephant and Castle to Clapham and Tooting on the map. I was knocked off there earlier in the year, and the LCC said it has the most dangerous junction for cyclists in London on it. https:&#x2F
51.
by riv991 3y ago
Previously we had no limit. We observed gains in both latency and throughput by implementing Automaxprocs and decided to roll it out widely. This aligns with what others have reported on the Go runtime issue open for this. "When go.ube
52.
by riv991 3y ago
I love ko, so simple to get a container running in one line and now integrated with GoReleaser. `docker run $(ko build -L main.go)`
53.
by riv991 3y ago
I've seen significant performance gains from this in production. Other people have encountered it too hence libraries like Automaxprocs existing and issues being open with Go for it.
54.
by riv991 3y ago
I intended it to be applicable to all containerised environments. Docker is just easiest on my local machine. I still believe it's best to set these variables regardless of cpu limits and/or cpu shares
55.
by riv991 3y ago
Hi I'm the blog author, thanks for the feedback I'll try and clarify this. I think this is how the sympton presents but I should be clearer.
56.
Go, Containers, and the Linux Scheduler(riverphillips.dev)
3 points by riv991 3y ago|0 comments
57.
The Advantages of Queues on Logs(jack-vanlightly.com)
13 points by riv991 3y ago|0 comments
58.
Demystifying Database Transactions(dineshgowda.com)
3 points by riv991 3y ago|0 comments
59.
by riv991 3y ago
The feature I'd love is history. I'd like to know if my builds are getting slower over time. I'd be able to detect flaky tests automatically. It seems basic, but I know third-party solutions exist for this. It's out of t
60.
by riv991 3y ago
I think Open Telemetry has solved the stream processing problem issue with span links[1]. Treating each unit of work as an individual trace but being able to combine them and see a causal relationship. Slack published a blog about it pretty

More ›