Lightnews — Scholar-powered news

Reposted

fig (aka: [phil]) @bad-example.com · 19h

constellation runs on a bare metal server with 4 dedicated CPU cores, 16GiB memory, 1TiB fast NVMe SSD attached, and 500mbit unmetered network connection.

Why @why.bsky.team · 1d

turns out raspberry pis are really fast these days

2 3 44

fjallrs.bsky.social @fjallrs.bsky.social · 3d

**slightly slower in reading

2

fjallrs.bsky.social @fjallrs.bsky.social · 3d

*bench tool

1

fjallrs.bsky.social @fjallrs.bsky.social · 3d

sled (bloodstone) is not in the bench too rn, because you can't compile it next to sled w/ compression; plus it's super unstable - in general I found it to be faster in writing, smaller on disk, but similar or slightly slower in writing than sled 0.x...

2 2

fjallrs.bsky.social @fjallrs.bsky.social · 3d

Blob GC working again (now fully automatic) - much less impact on foreground work (old GC was stop-the-world)

1 8

fjallrs.bsky.social @fjallrs.bsky.social · 6d

Hopefully I will have results in 6 hours 👀

1 3

fjallrs.bsky.social @fjallrs.bsky.social · 6d

Noo 🥲

I wanted to expand it to a 1-hour run but it crashed because of a bug in the workload (I think), in the middle of the night.

1 2

fjallrs.bsky.social @fjallrs.bsky.social · 6d

Fun coloured bars and lines

3 4 6

Reposted

fjallrs.bsky.social @fjallrs.bsky.social · 12d

If you sponsor NOW (github.com/sponsors/fja...), you can get an exclusive preview of version 3!!

jk I pushed the first pre-release to crates.io - it's unstable though! Breakages guaranteed, and some APIs are missing!

bye

Sponsor @fjall-rs on GitHub Sponsors

Support fjall-rs's open source work

github.com

6 8

fjallrs.bsky.social @fjallrs.bsky.social · 12d

If you sponsor NOW (github.com/sponsors/fja...), you can get an exclusive preview of version 3!!

jk I pushed the first pre-release to crates.io - it's unstable though! Breakages guaranteed, and some APIs are missing!

bye

Sponsor @fjall-rs on GitHub Sponsors

Support fjall-rs's open source work

github.com

6 8

fjallrs.bsky.social @fjallrs.bsky.social · 12d

Looks like the default fillfactor is 100%, which should be good for disk space. So it's probably dead row overhead and lack of page compression (?) plus maybe secondary indexes.

1 1

fjallrs.bsky.social @fjallrs.bsky.social · 14d

But yeah, it feels like things are slotting into place.

I have more than 50 git stashes and branches floating around... it's been a bit messy, but getting there.

fjallrs.bsky.social @fjallrs.bsky.social · 14d

I think I was lucky to fall into the pit of success because I think I made more progress the last two days than the last two months combined...

V3 pre-release(s) very soon... 👀

1 2

fjallrs.bsky.social @fjallrs.bsky.social · 16d

Add to that, sweeping API changes for better ergonomics that easily touch over a hundred files - Rust's doctests are a godsend here, I would have gone insane already without them

1 2

fjallrs.bsky.social @fjallrs.bsky.social · 16d

ngl v3 is a bit more involved than I originally planned or anticipated; I don't want breaking changes for a while, so it becomes this chase of making sure everything is really future-proof

1 3

fjallrs.bsky.social @fjallrs.bsky.social · 20d

Yeah a little bit; new disk format, changed some APIs to be nicer etc. etc.

1

fjallrs.bsky.social @fjallrs.bsky.social · 20d

I will never do a major release like this again

1 1 6

fjallrs.bsky.social @fjallrs.bsky.social · 21d

Maybe it was migrated to Server 2025? github.com/actions/runn...

Windows-latest workflows will use Windows Server 2025 image in GH · Issue #12677 · actions/runner-images

Breaking changes Windows Server 2025 image is ready to be the default version for the Windows-latest label in GitHub Actions Target date This change will be rolled out over a period of several week...

github.com

1

fjallrs.bsky.social @fjallrs.bsky.social · 22d

I really dread having to some day write a quick_cache replacement, tailored for lsm-tree

1

fjallrs.bsky.social @fjallrs.bsky.social · 29d

Ubuntu 22.04.5 - only really using write(), fsync() and pread()

3

fjallrs.bsky.social @fjallrs.bsky.social · 29d

Nvm getting corruptions on XFS too... sooo... kernel bug??

1 3

fjallrs.bsky.social @fjallrs.bsky.social · Sep 6

friendship with ext4 ended, xfs is my new best friend

(whyyy is ext4 still giving me corruptions sometimes, even after updating my kernel??)

1 4

fjallrs.bsky.social @fjallrs.bsky.social · Sep 6

Yeah, that's a bit better

1 2

fjallrs.bsky.social @fjallrs.bsky.social · Aug 24

For weeks I've been regularly getting corruptions while running benchmarks... for RocksDB, too. It's infuriating because running a 15min+ benchmark is a coin flip whether it completes.

Seems like it was an issue with my arguably outdated Linux kernel... there were ext4 corruption bugs a while ago.

4

Reposted

Ryan Carniato @ryansolid.bsky.social · Aug 14

For a framework renowned for its innovation, it is funny how little Solid has changed in the last 7 years. Yeah we've innovated on features, fine-grained concurrency/hydration, streaming, server functions, single flight mutations, but the core tech and structure are untouched.

1 1 37