Hacker Newsnew | past | comments | ask | show | jobs | submit | dveeden2's commentslogin

Also easy to see why Ctrl-D works for exiting sessions.

The video from the presentation on this: https://youtu.be/tdx9leN2kBg?si=uYa7xsOvpoonjaxB

This was part of the MySQL Belgian Days that was organized in the days before FOSDEM.


Any slides maybe?



> There you go. It’s 5PM. It’s always 5PM.

That reminded me of the Go Playground, where it is always 2009

https://go.dev/play/p/VrWYHGbtc6m


Yes, TiDB has columnar data and also Vector support. All open source and MySQL compatible.


Good time to consider TiDB or MariaDB.


Anything new? A new release?


Things that I noticed are not yet there in this version: /proc, uptime, uname

Things that are working: `cal 2026`, coredumps

Things that might be broken or aren't working as expected: ps (only returns "No mem")

And utmp is in /tmp?

And no /usr/sbin or /sbin? And nothing in /usr/local?

The messages from `write root` are only in uppercase.


/proc is a Linux thing.


/proc is only copied (and extended) by Linux. It was introduced in UNIX V8. It is also in Solaris and FreeBSD.


Unix v8 it's basically pre-plan9.


Oh. I was not aware of that


Maybe `pv` with the `--rate-limit` option can be used for the buffer problems?


Other databases written in Go:

- TiDB by PingCAP

- Vitess by PlanetScale

Both are basically only the SQL part as TiDB uses TiKV (written in Rust) and Vitess uses MySQL.

For those who want to implement a database in Go but without having to implement a network protocol there is go-mysql, which allows you to do this: https://github.com/go-mysql-org/go-mysql/blob/master/cmd/go-... As demonstration I created a networked SQLite: https://github.com/dveeden/go-mysql-examples/blob/main/go-my...

Both TiDB and Vitess have parsers that can be used outside standalone. So if you only want to implement your own on disk format, this can help.

Note that I'm working for PingCAP on TiDB and I'm also a co-maintainer for go-mysql.


We use Tidb at work at scale. Great product! Was looking at the source today to understand an error code.


Vitess came from YouTube


Didn't the Vitess team found planetscale?


Yes! The founders of PlanetScale were the co-creators of Vitess at YouTube, where it was built to handle MySQL scalability. PlanetScale builds on Vitess but offers a managed, developer-friendly experience.


Wasn't something like HOMA already tried with SCTP?


And QUIC. And that thing tesla presented recently, with custom silicon even.

And as usual, hardware gets faster, better and cheaper over the next years and suddenly the problem isn't a problem anymore - if it even ever was for the vast majority of applications. We only recently got a new fleet of compute nodes with 100gbit NICs. The previous one only had 10, plus omnipath. We're going ethernet only this time.

I remember when saturating 10gbit/s was a challenge. This time around, reaching line speed with tcp, the server didn't even break a sweat. No jumbo frames, no fiddling with tunables. And that actually was while testing with 4 years old xeon boxes, not even the final hw.

Again, I can see how there are use cases that benefit from even lower latency, but thats a niche compared to all DC business, and I'd assume you might just want rdma in that case, instead of optimizing on top of ethernet or IP.


This is a solid answer, as someone on the ground. TCP is not the bogeyman people point it out to be. It's the poison apple where some folks are looking for low hanging fruit.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: