MemoryStore Analytics seem inaccurate/unreliable

My MemoryStore analytics show that I am not even close to hitting my limits.

Usage:

Requests:

Given that I’m barely at 1% utilization on these charts, you’d expect smooth sailing. Let’s check our response chart:

Failure Status Requests:

These analytics show only 3 non-successful requests over the last 7 days, which is definitely the smooth sailing we anticipated. 1 TotalRequestsOverLimit, which is strange when the above graph shows my request count nowhere near the limit. 2 InternalError, which is annoying but no big deal. Cool.

Then we go to my error logs and search for “MemoryStoreService”… and it tells a different story.
image

MemoryStores are failing far more than the above graphs are claiming.

By my error log counts, I’m seeing a very different story. I’m not going through 20 pages of error logs and adding up the counts, but I can assure you it’s a lot higher than 3.

Expected behavior

I have several expectations that are not being met:

  1. MemoryStoreService should be a lot more reliable- this is an unacceptable amount of InternalError responses.
  2. My analytics should reflect my true situation. I am unsure what my real utilization is. Are the throttling errors mistaken, or am I overutilizing?
  3. MemoryStoreService errors are quite unhelpful.
    MemoryStoreService: InternalError: Internal Error. does not provide any insight into what is going wrong and how I can work around it.
    RequestThrottled: Recent MemoryStores requests hit one or more limits. Are my total requests too high, or is it failing because I hit the limit for a single queue/map?

Page URL: https://create.roblox.com/dashboard/creations/experiences/537069295/analytics/memory-stores?granularity=Hourly&rangeType=Last7Days

12 Likes

Thanks for the report! We’ll follow up when we have an update for you.

3 Likes

The error still exists, I encountered it yesterday and it really spoiled my mood.
Also, in my game, the quota did not exceed a total of 2%, there were jumps, but they did not exceed it, but still there were many errors related to the fact that somehow the quota was exceeded, which leads me into confusion.




1 Like

And I also encounter another error.

2 Likes

Hi there, updating this thread to reflect on some changes we have worked on

  • We were able to identify and fix the high number of internal error responses.
  • The throttling errors were accurate before, although the order in which they were reported was not ideal. Your analytics have now been updated to reflect true resource utilization.

We have a longer-term project to make these as close to 100% accurate and reliable as possible, but the discrepancies outlined in this bug report should be fixed now. Please feel free to file another bug in case you notice any issues in your MemoryStores usage or in the analytics you view on the dashboard.

Thank you!

4 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.