You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One common misconception about karafka multi-threading is that it works like Sidekiqs. The tricky part is, that it works and it does not work similarly. Aside from explaining, etc we could provide a metric/stats in web-ui per process on their real-time ability to operate in multi-threading. It's not the same as utilization, because utilization takes into consideration work time but here we would be interested only in polling ability/reduction of threading potential.
The text was updated successfully, but these errors were encountered:
One common misconception about karafka multi-threading is that it works like Sidekiqs. The tricky part is, that it works and it does not work similarly. Aside from explaining, etc we could provide a metric/stats in web-ui per process on their real-time ability to operate in multi-threading. It's not the same as utilization, because utilization takes into consideration work time but here we would be interested only in polling ability/reduction of threading potential.
The text was updated successfully, but these errors were encountered: