ivandika3 commented on PR #5288: URL: https://github.com/apache/ozone/pull/5288#issuecomment-3241832755
> Unfortunately, LINEARIZABLE was worse than DEFAULT when I ran the same ozone freon ockrw ... command mixed read and write through multiple clients. LINEARIZABLE: read qps: 1.5k, write qps: 2.4k; DEFAULT: read qps: 8.7k, write qps: 2.8k. Although this does not meet the throughput limit, it is also not as expected. The main issue is that although LINEARIZABLE read increases throughput the pure-read workloads, it will cause overall lower throughput and worse performance in mixed-write workloads. Although technically this can be merged without any issues, we want to first understand this large performance decrease (whether it's actually due to the inherent issue that comes Raft linearizable read or some other reasons). Additionally, enabling server-side LINEARIZABLE read without the corresponding change in the client (i.e. `OMFailoverProxyProviderBase` and relevant classes) means that most clients will revert back to the original read / write from leaders. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
