• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Could not read from server cache
It's not a bug, but "Could not read from server cache" and reading / contacting instance directly seems to take longer time ... 

I know I've read something about the cache before... Anyway to reset that, or what do we do if we find that the cache can not be read?

Br /John
Hi John,

The libraries check the cache by default for reads and syncs as a performance enhancement and has little to no effect if the cache isn't there. The cache system is currently disabled on all regions. Because of this, the cache is not being populated so you see the "could not read from server cache" messages. We have been testing and improving the cache system on a private region. You will see a performance boost once the cache system is reengaged on all regions.

Forum Jump:

Users browsing this thread: 1 Guest(s)