多线程尾端正在降低 Chronicle Queue 的读取性能

Question

Hi guys I have developed a multithread application that use Chronicle Queue to persist the data exchanged. For each thread I create a new chronicle queue instance, all of than pointing to the same file. When the number of the threads increase (or the number of tailers) the reading performance is impacted. I am using a regular chronicle single binary queue with default read/write lock. Could some one face a similar issue like that before? All of my threads are reading the queue in a busy spin mode.

Answer 1

You don't have to create a Chronicle queue per thread. You can create a single instance of Chronicle queue, then for each thread, create a tailer by calling createTailer. So it is only the tailer that you have to have per thread. Not the queue. Please try that and let me know if it helps.