chore: metaverse benchmark scenario#1043
Open
guitarrapc wants to merge 48 commits into
Open
Conversation
- Remove 60FPS - 30FPS for 500, 800, 1000 clients - 15FPS for 500, 800, 1000, 2000 clients
This reverts commit 3c4e99c.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Added a Metaverse benchmark scenario that synchronizes Vector3 positions for a specified FPS and number of clients.
While the broadcast scenario is simply a server-to-client broadcast, the Metaverse scenario is a mixture of "client-to-server position updates" and "server-to-client broadcasts."
This scenario is intended to simulate high bandwidth usage; therefore, broadcast throttling (when the position has not changed) is intentionally not implemented. All clients always update their positions, and the server broadcasts to all clients on specified fps.