Proposed: Stress Testing Godot Engine’s Networking System

Context

The V-Sekai development team is working on a project that involves avatar, world, and prop collaboration workflow in the Godot engine. The team plans to use FoundationDB with SQLite to enhance the performance of this workflow.

Problem Statement

We need to ensure that the networking system of the Godot engine can handle the increased load and perform optimally under stress.

Solution

Create in three stages:

local client to local server
local client to remote server
remote client to remote server

Does not test infrastructure implementation.

We propose to conduct stress testing on the Godot engine’s networking system.

This will involve creating multiple virtual users and simulating high traffic scenarios to evaluate how the system performs under heavy load.

# This is a single node example.
# Assuming we have a list of props and a World instance
var props = [prop1, prop2, prop3]
var world = World.new()

for i in range(10): # Simulate 10 users
    var user = User.new() # Create a new user
    var selected_props = [] # List to store selected props

    for _ in range(randi()%props.size()+1): # Randomly select props
        var prop = props[randi()%props.size()]
        selected_props.append(prop)

    user.glue_props(selected_props) # Glue selected props together
    world.merge(user.get_changed_world()) # Merge the changed world into the main world

# Now, let's read back the changed world
print(world.get_state())

# To be determined realistic multclient version.

Test personal computer and digital ocean.

Benefits

Identify potential bottlenecks in the system.
Ensure the system can handle high traffic without compromising performance.
Improve overall system reliability and user experience.

Downsides

Requires time and resources to set up and conduct the tests.
Potential for false positives or negatives due to the simulated nature of the test.

The Road Not Taken

An alternative would be to skip stress testing and directly implement the system. However, this could lead to unforeseen issues in a live environment, potentially affecting user experience.

The Infrequent Use Case

In cases where the traffic is consistently low, stress testing may not provide significant benefits. However, it’s still important to prepare for potential spikes in usage.

In Core and Done by Us

The proposed stress testing will be conducted by the V-Sekai development team.

Status

Status: Proposed

Decision Makers

V-Sekai development team