Pinging @anoek again, although he has certainly other, more important fish to fry.
@BHydden I don’t think it’s a data base issue. Since deployment on new servers yesterday, the access to ladder pages is far better, but the ranking bug is still there. I suspect it’s linked to the way the computing of new ranks after the victory in a challenge works. One thing is sure, it is that the way it works, once such an error (two identical ranks) is introduced, it is not corrected when new ranks are computed. Since my first post, I have winned a challenge and jumped higher in the ladder. The player skala above me took my rank, and as of today skala and carokarm are both #354. Which means when new ranks are computed, there is no verification of possible duplicates. So, two things might/should be done IMHO.
- Correct the current glitches by running a specific script checking for duplicates and pushing the ranks downward accordingly.
- The above is just a patch, and does not explain the origin of those glitches, which seem quite random. The origin has to be searched in the way the data base is updated after a winned challenge, is there an in-memory computing followed by a batch update, or is the data base directly updated, one player at a time? In any case, my hunch is that duplicates were caused by conflicting simultaneous updates.
I just ported this conversation under “support” category, where it belongs.
Please follow-up there. Thanks.