Skip to main content

Memory Stability Test

This benchmark validates that Solvix maintains stable memory usage over repeated and high-volume request cycles.

Why Memory Stability Matters​

In production systems:

  • Memory leaks lead to crashes
  • Long-running services degrade over time
  • Serverless environments get expensive
  • Containers restart unexpectedly

A stable HTTP client must ensure no unbounded memory growth.

Test Objective​

To verify:

  • No memory leaks across repeated executions
  • Garbage collection works correctly
  • Internal queues are cleaned properly
  • No retained references after request completion

Test Setup​

  • Runtime: Node.js
  • Requests per round: 10,000
  • Total rounds: 3
  • Tooling: Manual heap measurement
  • Transport: Mock / lightweight HTTP

Test Code​

import { createClient } from "solvix";

const client = createClient({
  baseURL: "https://example.com",
});

function getMemoryMB() {
  return (process.memoryUsage().heapUsed / 1024 / 1024).toFixed(2);
}

async function runTest() {
  console.log("Initial Heap:", getMemoryMB(), "MB");

  for (let round = 1; round <= 3; round++) {
    console.log(`Round ${round} start:`, getMemoryMB(), "MB");

    for (let i = 0; i < 10000; i++) {
      await client.get("/test");
    }

    global.gc?.(); // force GC if enabled

    console.log(`Round ${round} end:`, getMemoryMB(), "MB");
  }
}

runTest();

Results​

Initial Heap: 7.03 MB

Round 1 start: 7.03 MB
Round 1 end: 10.10 MB

Round 2 start: 10.07 MB
Round 2 end: 10.14 MB

Round 3 start: 10.06 MB
Round 3 end: 10.15 MB

Analysis​

Observations​

  • Initial increase due to warm-up and caching
  • Memory stabilizes after first round
  • No continuous growth across rounds
  • Heap remains nearly constant

Interpretation​

This indicates:

  • No memory leaks
  • Proper cleanup of internal structures
  • Efficient lifecycle management

Internal Mechanisms That Help​

Solvix ensures memory stability via:

  • Clearing queues after execution
  • Weak references where applicable
  • No global state accumulation
  • Controlled lifecycle of retry & dedupe maps

Real-World Impact​

This behavior is critical for:

  • Long-running backend services
  • Microservices
  • Serverless environments
  • Edge runtimes

Best Practices​

  • Avoid storing large payloads in memory
  • Use streaming when possible
  • Enable GC in stress testing
  • Monitor memory in production

Conclusion​

Solvix demonstrates strong memory stability, making it safe for:

  • High-load systems
  • Continuous execution environments
  • Production-grade deployments