slow message loading when topic is compacted and filter is oldest

[wanisfahmyDE]

Issue submitter TODO list

• I've looked up my issue in FAQ
• I've searched for an already existing issues here
• I've tried running main-labeled docker image and the issue still persists there
• I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

We have several compacted (cleanup policy: compact) topics in our clusters, when we try to load messages in any of them using the "oldest" filter, it takes a significant amount of time to load (around 1 minute or more). Worthy to note that this doesn't occur when selecting the "newest" filter.

The topic size is around 17MB.

We monitored the CPU and memory of kafbat and increased it significantly in efforts to get a faster load time, but it didn't help. The app logs and console logs looks normal

We have significantly larger topics that are not compacted and they load the messages instantly, regardless of which filter.

Expected behavior

messages in compacted topics are loaded faster, like normal topics that have delete cleanup policy

Your installation details

running the latest main 1196f9f docker image deployed in EKS as a normal k8s deployment without helm.

Steps to reproduce

create a compacted topic and load it with some significant data

Screenshots

Logs

No response

Additional context

No response

[github-actions]

Hi wanisfahmyDE! 👋

Welcome, and thank you for opening your first issue in the repo!

Please wait for triaging by our maintainers.

As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues.
Sponsorship link

If you plan to raise a PR for this issue, please take a look at our contributing guide.

[xuyuanz]

Similar problem we noticed: for compact topics, oldest is working fine for us. But when we switched to use newest, it took forever to load.

[iliax]

@Haarolean this should be fixed due to #406

[Haarolean]

@Haarolean this should be fixed due to #406

@wanisfahmyDE @xuyuanz please verify, the image is available under ghcr.io/kafbat/kafka-ui:main

[kapybro]

Further user feedback is requested. Please reply within 7 days or we might close the issue.

[wanisfahmyDE]

hey @Haarolean, yes the image is ghcr.io/kafbat/kafka-ui:main. the commit SHA is 1196f9f

[kapybro]

Thanks for the additional feedback! We'll get back to your issue soon.

[Haarolean]

@wanisfahmyDE so does it work now?

[wanisfahmyDE]

no it doesn't, I created the issue when we were running already on ghcr.io/kafbat/kafka-ui:main