Re: [I] High GC pause cases high publish latency [pulsar]

2024-07-06 Thread via GitHub
dao-jun closed issue #22866: High GC pause cases high publish latency URL: https://github.com/apache/pulsar/issues/22866 -- 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

Re: [I] High GC pause cases high publish latency [pulsar]

2024-06-13 Thread via GitHub
lhotari commented on issue #22866: URL: https://github.com/apache/pulsar/issues/22866#issuecomment-2167218549 > I think so. But we might need to improve here to avoid allocating a very large `long[]` to give GC pressure. :) One alternative would be to switch to use

Re: [I] High GC pause cases high publish latency [pulsar]

2024-06-06 Thread via GitHub
mattisonchao commented on issue #22866: URL: https://github.com/apache/pulsar/issues/22866#issuecomment-2154038308 >Btw. The metric might be wrong. It's not necessarily pause time, but GC time that happens in the background. See https://github.com/apache/pulsar/pull/18891 I

Re: [I] High GC pause cases high publish latency [pulsar]

2024-06-06 Thread via GitHub
lhotari commented on issue #22866: URL: https://github.com/apache/pulsar/issues/22866#issuecomment-2154013458 Btw. The metric might be wrong. It's not necessarily pause time, but GC time that happens in the background. -- This is an automated message from the Apache Git Service. To

[I] High GC pause cases high publish latency [pulsar]

2024-06-06 Thread via GitHub
shibd opened a new issue, #22866: URL: https://github.com/apache/pulsar/issues/22866 ### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Motivation We have observed that using Individual