Getting the actual message count might be more complicated: #39127.
/cc @alexander-schranz fyi

@chalasr yes xlen does not represent the number which somebody would expect. It requires another logic. See comment here: #31545 (comment). I know that xinfo format changed between versions of the php redis extension, so it is not easy task here. So there need to be checked how to implement this for different versions. Also there could be that they did add a easier way to get the correct value. I did not yet update myself about the changes in the streams in Redis 6.

Thanks @alexander-schranz ! I updated my code.

But, I am wondering if we have to limit xRange results to 1000 (for example) in order to limit memory usage and use the last element to get the next "page" (like using a SCAN).

I did have a look at the latest changes about redis. The new version Redis 7 provides entries_read and lag.

redis/redis#9127
https://redis.io/commands/xinfo-groups/

Not 100% sure but could be that lag provide the information we need.

I ran tests on a Redis 7.x a lag seems to do the job !

Thank you @Jean-Beru.

Good work @Jean-Beru 👍

Thanks a lot for your help @alexander-schranz !