5 ms·
Ive always used the feature(?) allowing you to mount parts of the fs read-write persistent on the local disk which might help the sqlite issue, though not sure
by ronniefalcon 10mo ago
Ive always used the feature(?) allowing you to mount parts of the fs read-write persistent on the local disk which might help the sqlite issue, though not sure if thats a read/write issue or something else.
Have never used scsi for this. i suspect it's faster?
- ahepp 10mo ago> Ive always used the feature(?) allowing you to mount parts of the fs read-write persistent on the local disk which might help the sqlite issue, though not sure if thats a read/write issue or something else. The entire nfs based rootfs is mounted rw at this point, so it's not simply a matter of it being a read-only filesystem. NFS has some weird file locking behavior that makes it behave noticeably different from a local filesystem for certain functions. Some sources seem to claim NFSv4 has better support for file locking, but I was unable to get root-on-nfs working reliably under any permutation of NFS parameters I attempted. Loading the NFS rootfs wasn't a problem though, so I figure a distro that was a bit more intentional about not making nfs-unfriendly software part of the core would be able to do it. Although I also tried setting up Arch in this way and had similar issues. > Have never used scsi for this. i suspect it's faster? I'm not really sure whether it's faster. A lot of online sources say "iscsi is faster because block device" and it's not immediately obvious to me how that would make it faster. I would say that in my experience iSCSI has had fewer compatibility issues. Applications seem to be happier with a high latency block device and a traditional filesystem, than doing file operations over the network.