Probably the physical keyboard?

I’d say it’s a pretty big differentiator

Yes, and the difference being that they did not build a huge wall between them.

Mild correction, but unless you're talking about something in Columbia or maybe Panama, I think what you're referring to is between North American countries.

Back in the day, they migrated away, only to be brought back as diesel fuel today. ;)

And finally end up with either jemalloc or possibly mimalloc. ;)

we actually ended up with (new) tcmalloc.

for us, tc was among the fastest in runtime while being very space efficient [0]. large rust application using far too many threads.

we’ve since also had great success with tc’s built in profiling tools.

[0]: https://news.ycombinator.com/item?id=47403847

Interesting, is there an accompanying article?

We've tried tcmalloc, too. I don't remember the exact details, but we basically ended using jemalloc because it was using way less memory.

Same story with mimalloc - it usually provided a tiny bit more speed, but required more cpu and memory.

no article, sorry, grabbed the numbers from an old PR.

to confirm, you were using tcmalloc from https://github.com/google/tcmalloc and not from https://github.com/gperftools/gperftools, right?

the latter is a lot worse iiuc.

Good point. It was from the https://packages.debian.org/trixie/google-perftools Debian package, which points to the gperftools project - so it was the worse one I guess.

yeah that’s a common mistake when evaluating tcmalloc. gperftools tcmalloc diverged quite a while ago. doesn’t have a lot of the fancier features of modern tcmalloc [0].

[0]: https://github.com/google/tcmalloc/blob/master/docs/gperftoo...

Invariably so but I'm mulling over malloc()s on embedded topic now.

    Several metrics are actually growing exponentially.

Power consumption and water consuption are the obvious ones. What are the others?

Do you want to understand what this obsession is about? You probably need to visit Japan more.

I read that as a statement that says something along the (nowadays very tired) line that the cloud is not magical, it's just other people's computers.

Yes, but try rsync instead of scp. Mind the slash though!

Both rsync -avz /path/to/file user@server:/another/path/to/ or rsync -avz /path/to/file/ user@server:/another/path/to/file

Will create directory named /another/path/to/file which will contain all contents of the original directory (/path/to/file/*).

Basically, if you include the trailing slash in the source path, only contents of the directory will be copied (useful when you need to rename it).

    rsync -avz path/to/old_dir/ user@server:/path/to/new_dir

If you omit the trailing slash in the source path, rsync will create the target directory for you. See man rsync for more info.

Exactly. And there is a lot of other alternatives in this space, check the guides at https://runrepeat.com/