You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I've had endless fun debugging Mixer calls to find out why with the latest changes and our caching in place the Mixer hits the adapter twice for each incoming HTTP request. Thanks to our caching though we basically pay no price for this as the second call returns in about 0.2ms on average which is peanuts but still annoying. I don't think it's a good idea to waste any more dev cycles on this, so will park the issue here for posterity.
The text was updated successfully, but these errors were encountered:
Oh, almost forgot to mention. It doesn't happen consistently. Sometimes if you try again the exact same HTTP request later, the Mixer only calls the adapter once. Go figure, how fun!
So I've had endless fun debugging Mixer calls to find out why with the latest changes and our caching in place the Mixer hits the adapter twice for each incoming HTTP request. Thanks to our caching though we basically pay no price for this as the second call returns in about
0.2ms
on average which is peanuts but still annoying. I don't think it's a good idea to waste any more dev cycles on this, so will park the issue here for posterity.The text was updated successfully, but these errors were encountered: