Unusual High Network Recv Values and POST Requests from Player Service Causing Lag in Low-Activity Places

I am experiencing significant lag due to network clogging in an experience I’m currently developing. This issue manifests as unusually high Recv values on the client side, even in an 80% empty place with only 2 players connected and no apparent activity. Upon investigation using the console, I observed that the lag appears to be caused by many POST requests being sent from the Player Service. These requests seem correlated to the number of players connected.

Steps to reproduce the issue:

Here’s how you can fill out the bug report:

Title
Unusual High Network Recv Values and POST Requests from Player Service Causing Lag in Low-Activity Places

Describe the issue
I am experiencing significant lag due to network clogging in an experience I’m currently developing. This issue manifests as unusually high Recv values on the client side, even in an 80% empty place with only 2 players connected and no apparent activity. Upon investigation using the console, I observed that the lag appears to be caused by a large number of POST requests being sent from the Player Service. These requests seem correlated to the number of players connected.

Steps to reproduce the issue:

Open the affected experience with a near-empty map.
Connect 1-3 players to the experience.
Monitor network performance using the client console (F9).
Observe high Recv values (e.g., ~50kb/s per player connected).
Notice that the issue resolves when POST requests stop, and Recv values drop to expected levels.
Additional observations:

The number of POST requests and network clogging increase linearly with the number of players.
No intentional data is being sent to clients from the server during this period.

Expected behavior

I expect Recv values to remain at normal levels (~10kb/s per player) in near-empty places with minimal activity. POST requests from Player Service should not cause excessive network usage under these conditions.

A private message is associated with this bug report

2 Likes

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