unpartitioned

One thing to realize is that a partitioned log is a generalization of an unpartitioned log (i.e.

Next, you don't have to over-provision unpartitioned space AND preserve 20% of partitioned free space.

Leaving part of the drive unpartitioned, or creating a partition but not putting a filesystem in it will accomplish that purpose.

It impossible to deny this when you have a GB+ sized area of unpartitioned data (or unmounted partition) containing seemingly random noise.

You can simply leave a portion of the drive unpartitioned This doesn't sound right.

On the unpartitioned SSDs/HDDs I use file systems like XFS, UFS or ZFS, which could not be used with Windows anyway.

And unless I'm really space-constrained, I'll leave some unpartitioned space as well, for later flexibility.

I format directly the raw unpartitioned SSD/HDD with a file system that uses 100% of the capacity, with no wasted sectors.

I'll restate my narrative: Single instance, normalized, unpartitioned databases run into scaling problems the several-hundred million row range especially when under heavy concurrent load.

I wish that it was easier to trim unused unpartitioned space.

You're benefiting from a massive open, unpartitioned platform (meaning, anyone can join and form communities/reply-to tweets, without isolating things to friend-groups or creating 'subreddits' with human moderators gatekeeping them).

This shouldn't imply access is unpartitioned.

On a "flat", unpartitioned table with the same data, pruning drops to ca.

This is why Windows, in particular, exhibits curious behavior when dealing with flash drives: It assigns a drive letter to a flash drive even if it contains no partitions — MS-DOS and Windows floppies, "superfloppies", and optical media were traditionally unpartitioned.

If you'd like to make this kind of testing possible, it would be useful to state as many 'positive' rules as possible, which Redis Cluster should always respect -- things like "if a majority of nodes are fully connected, they should always accept writes" and "an unpartitioned cluster should always agree on the same value" -- alongside the documentation on ways it might fail.