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.
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.2mson 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.