d/ Deplexo LIMIT LABConnecting

FREE TIER / RESOURCE TESTING

Find the boundaries.

Apply a controlled workload. Watch what the container allows.

Set LAB_TOKEN in Deplexo to keep access across restarts. The token stays in this browser tab.

CPU usage—Reading container quota
Memory used—Includes workers and page cache
CPU throttling—Throttled periods since container start
Memory OOM kills—Waiting for container

Run a test

Free plan: 0.25 CPU · 128 MB RAM · 250 MB disk · 10 Mbit/s · 100 GB/month

01COMPUTE

CPU saturation

Keep cores busy and measure quota throttling. One worker is enough to saturate 0.25 CPU.

02MEMORY

Memory pressure

Allocate real, touched pages. Start at 32 MiB, then try 64, 96, 128, and 160 MiB.

The app itself uses RAM too. Crossing the cap can kill a worker or restart the entire container.

03STORAGE

Disk capacity

Write real random data and sync to storage. Test 32, 128, 240, then 260 MiB on /data.

Files are removed after each run. On tmpfs, writes also consume memory. Duration includes writing.

04NETWORK

Speed & transfer

Stream data between this browser and your app. A 10 Mbit/s cap is about 1.25 MB/s.

Stops after 5 minutes or the chosen amount. Uses real transfer quota. Results also depend on your connection and the proxy.

Ready for a transfer

Persistent storage

Write files now. Restart your app in Deplexo. Come back and check they are still here.

—saved by this lab
05KEEP UNTIL DELETED

Save test data

Writes random data to /data. Finished files stay until you delete them, including after an app restart.

A stopped or failed write keeps its partial file too. Persistence requires the same mounted data volume; deleting the app may remove that volume.

Saved files

Connect to inspect persistent files.

No saved files yet.

These files count toward disk usage. The total covers this lab’s saved files, not every file on your volume.

Test journal

Exit status, workload progress, and cgroup snapshots.

Your first test will appear here.

Storage visibility

Used, free, and total space describe the filesystem, which may be shared with other apps. For this lab’s saved-file usage, see Persistent storage above. These filesystem figures do not establish your app’s disk quota.

What to verify outside this app

  • App count: attempt to create a second app on the same free account.
  • Monthly transfer: compare usage in Deplexo before and after a known transfer. To test exhaustion, seed a test account near its quota in your backend, then cross it with a small transfer.
  • Scope: use a paid test account with two apps to check whether resources are per app or shared.

Local transfer counters cover only lab payloads and reset on restart. They are not Deplexo’s billing meter.

Raw container telemetry
Waiting for telemetry…