@UC_Assist Well the booking was supposed to be at 5pm so it should be a joke that you rescheduled from your side and then you are asking me to pay a surge charge for your inconvenience? Scam much?
Hey @urbancompany_UC you changed a booking without notifying me and now you want to charge a surge charge? What joke is this, and your ai help is as dumb as it comes
@jorandirkgreef Since fille byte is aligned, and assuming the write is synced to disk, ideally for a non interrupted read only 0, 4096. unless something is buggy at device driver level where 512*n is still a possibility with classical format
@abhi9u@arpit_bhayani Many memory allocators Tc/je malloc work quite well with THP. Also they are quite bad in returning the memory back. Subtle bugs with madvise free are cherry on top
https://t.co/kr6zv74tmP
@arpit_bhayani Even with O_DIRECT & fsync storage devices could potentially acknowledge the command when they are in the device cache, (& power failure scenarios)so other than pulling out your Distributed Systems toolbox and doing some logging/journaling you literally can't ensure persistency
@wangbin579 Looks very interesting, at the read of abstract, similar to session guarantees paper for dist sys in db world, but still need to read the paper wholly
@abhishekcode42 For single precision floats, you'd miss after 24 Bits, so values after ~16 million (1<<24) will be incorrectly represented, you'd start rounding to the next 2, 4... etc for every subsequent bit.