Scalability issues

The conversation revolves around using a filesystem (ZFS) and the issues with the bdb backend that Bitcoin uses, which performs many I/O operations and writes them synchronously to disk. This process kills the caching provided by the filesystem. To solve this issue, the user needs to figure out how to turn off sync or determine if it is on for everything or just the wallet. It is advised to put ZFS's intent log on a separate SSD-backed device to get fast synchronous writes when running a large database on ZFS. The user suggests that Bitcoin's writes are likely small, so a RAM dev intent would be cheaper and faster than an SSD for that purpose. The discussion also touches on switching the Bitcoin block verifier to use a different style database layout ("ultraprune"), which is smaller, faster, and supports pruning. This approach deletes old blocks, transactions, and coins that have both been validated in the past and fully spent in the future since there is no need to validate further back beyond them unless you're a historian or have some other usage other than casual transactions.