HttpService reliability?

[EatSleepCodeRepeat (nem)]

My game incorporates an external server for the browsing of something close to a “global marketplace”. Roblox docs state the following:

• For each Roblox game server, there is a limit of 500 HTTP requests per minute. Exceeding this may cause request-sending functions to stall entirely for about 30 seconds.

At 8 players/server that limitation is okay with me but if I recall correctly I remember reading here about a year ago that there are some hidden restrictions to the HttpService such as not being able to send more than 3 requests at a time. Caching is not really an option as the game is already somewhat performance-consuming and the data is quite big. Queuing the requests is my last resort if this turns out to be true. I did try experimenting on my own but I couldn’t replicate the bug and I wanted to know if anyone has had such a problem with undocumented HttpService ratelimitng before? Is this the only undocumented ratelimit?

[diagrammatized]

Hi.
The only undocumented rate limit I’m aware of is the limit on the amount of data a place can upload via HttpService in a given month. If a place is only uploading small amounts of data, this limit is not likely to be reached.
If you’re exceeding the 500 requests per minute limit, you should try increasing the delay between requests. You can use HttpService:GetAsync() or HttpService:PostAsync() with a Delay value to enforce this delay. Setting a delay of 0 is equivalent to setting no delay and is not recommended.
local response = HttpService:GetAsync(“http://example.com/”, true, {Delay = 1})


Also, your profile picture…

[EatSleepCodeRepeat (nem)]

@diagrammatized

The only undocumented rate limit I’m aware of is the limit on the amount of data a place can upload via HttpService in a given month. If a place is only uploading small amounts of data, this limit is not

Update HttpService wiki page to indicate 3 concurrent connection limit

HTTP service has a maximum number of concurrent requests. This caused a bug in one of my plugins, where the user ended up with a bad UX & they had to wait a while for a request to get through. If I had known about this limit in advance, I could have rearchitected my system to minimize concurrent connections. Basically, my plugin needs to hear asynchronous updates from the server, and since I can’t open up my own TCP server in studio, I have to settle for doing HTTP long-polls to some HTTP serve…

@diagrammatized

If you’re exceeding the 500 requests per minute limit

I am not, it is way below that, it is just that there is a lot of data transmission. Bytes of data being sent and kilobytes received. I was just concerned about the concurrent request limit but I ended up using this module to limit that easily.

@diagrammatized

{Delay = 1}

didn’t even know this was a thing, but i have setup the http requests in a way that even if my servers are down, or there are too many http requests everything will be handled fine.

@diagrammatized

HttpService in a given month

In a given month? Never heard of that. This was the point of the post tbh to see what other limits are undocumented. Could you elaborate?

@diagrammatized

Also, your profile picture…