Skip to content

[Testing] WebSocket Load Testing and Connection Stability #170

Description

@AlAfiz

Description: Create a load-testing script capable of simulating 1,000+ concurrent WebSocket client connections subscribing to the live liquidity pool event feeds.
Context / Motivation: WebSockets are notoriously memory-intensive. We must empirically prove that our Node.js event loop can handle high concurrency during volatile market events without dropping connections or triggering an Out-Of-Memory (OOM) crash.
Acceptance Criteria: - [ ] Utilize a load-testing tool designed for WebSockets (e.g., Artillery or custom Node worker threads).

  • Script must simulate clients connecting, subscribing to random pool IDs, and listening for broadcast payloads.
  • Track and report the memory usage of the API server during the test.
  • Verify that broadcasting a single Swap event successfully reaches all 1,000 mock clients within 500ms.
    Technical Pointers: You may need to bypass default OS connection limits (ulimit) locally to simulate thousands of concurrent sockets.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardOfficial CampaignCampaign: Official Campaignhelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions