On Fri, Oct 1, 2021 at 4:37 PM Henrik Ingo <henrik.i...@datastax.com> wrote:
> A known optimization for the hot rows problem is to "hint" or manually > force clients to direct all updates to the hot row to the same node, > essentially making the system leader based. This allows the database to > start processing new updates even while the first one is still committing. > (See Galera for an example implementing this > <https://galeracluster.com/library/documentation/using-sr.html#usr-hot-records>.) > This makes me wonder whether there is a similar optimization for Accord > where transactions from the same coordinator can be allowed to commit > within the SkewMax window, because we can assume that the trx timestamps > originating at the same coordinator cannot arrive out of order when using > TPC? > > TCP -- Henrik Ingo +358 40 569 7354 <358405697354> [image: Visit us online.] <https://www.datastax.com/> [image: Visit us on Twitter.] <https://twitter.com/DataStaxEng> [image: Visit us on YouTube.] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.youtube.com_channel_UCqA6zOSMpQ55vvguq4Y0jAg&d=DwMFaQ&c=adz96Xi0w1RHqtPMowiL2g&r=IFj3MdIKYLLXIUhYdUGB0cTzTlxyCb7_VUmICBaYilU&m=bmIfaie9O3fWJAu6lESvWj3HajV4VFwgwgVuKmxKZmE&s=16sY48_kvIb7sRQORknZrr3V8iLTfemFKbMVNZhdwgw&e=> [image: Visit my LinkedIn profile.] <https://www.linkedin.com/in/heingo/>
