There are two scenarios of offset committing that we can improve:
1) we can filter the partitions whose committed offset is equal to the consumed offset, meaning there is no new consumed messages from this partition and hence we do not need to include this partition in the commit request.
2) we can make a commit request right after resetting to a fetch / consume position either according to the reset policy (e.g. on consumer starting up, or handling of out of range offset, etc), or through the
so that if the consumer fails right after these event, upon recovery it can restarts from the reset position instead of resetting again: this can lead to, for example, data loss if we use "largest" as reset policy while there are new messages coming to the fetching partitions.