Enumerating matches. Strange (slow) behavior.

I’m trying to loop through a players match history and have noticed a pattern with (slow) response times.

My process is as follows:

Step 1: Request the players first 25 matches (start=0, count=25)
Step 2: Check the number of returned matches. If the number of matches returned is 25; continue to Step 3, else; finish.
Step 3: Increment start by 25 and request another 25 matches (start=+25, count=25)
Step 4: Repeat from Step 2.

Here is an example timeline of requests: i.imgur.com/iCI2fuK.png

The first requests takes some amount of time, then following two requests are significantly faster. This pattern appears to repeats (i.e. every third request is slow).

I’m looking at some requests (the ones that take a long time) that can take as long as 20 seconds to complete. This behavior gets worse the further into a players history you get. Players with 10,000 matches and more are especially painful.

Is this behavior intentional?

Hi again Furiousn00b! We agree - this behavior seems odd and is not intentional. Do you have a sample gamertag to aid in our investigation? Thanks!