persistence reocrd on pool member

Just to level set, the chosen load balancing algorithm is responsible for dividing the traffic amongst pool members, and the persistence method is used to keep an existing "session" pinned to a single pool member after that initial load balancing decision. You may get close, but you'll likely never see exactly even distribution across the pool members, especially when persistence is involved.

Can you elaborate on the persistence and load balance methods you've selected? Depending on the persistence method, you can see the persistence record table from the command line.