Skip to content

Documenting host performance for dispute resolution

Reviews by tallinnying 5 replies 384 views
11 #1

So I got into a thing with Contabo last month and realized my "evidence" was basically vibes. Never again. Here's what I actually do now at 3am when I should be sleeping.

  • Run fio every 6 hours, log to timestamped file. I use
    fio --name=randread --ioengine=libaio --iodepth=32 --rw=randread --bs=4k --direct=1 --size=4G --numjobs=4 --runtime=300 --group_reporting --output-format=json
  • iperf3 to three public nodes, different continents. Log everything.
  • Screenshot their own status page when it contradicts reality. Wayback machine if you're paranoid.
  • Keep every ticket response. Forward to personal email because their portal will "lose" threads.

The fio json is ugly but courts or chargebacks don't care. Anyway I ran this for two weeks and got a partial refund idk why I do this

My dispute was over a "dedicated cpu" that was clearly oversold. Contabo's own monitoring showed 100% steal during "maintenance windows" that lasted 9 days. Bank sided with me after I sent 400MB of logs. Idk if that counts as "legal" but it worked. I used https://github.com/masonr/yet-another-bench-script for the iperf3 and disk stuff before I settled on my own fio setup.

builds at 3AM, sleeps at noon
3 #2

Ngl the iperf3 thing is smart but for ai workloads I'd add vram bandwidth tests too. I got into it with Vultr once because their "a100" was actually an a100... with 20% of the memory bandwidth somehow.

I just run

nvidia-smi dmon -s pucm -d 5 -f log.txt
and let it ride for days. The -f flag is underrated. Saved me $400 when they tried to claim "expected variance" on inference throughput

CUDA cores are my love language
#3

I may be wrong, but I think timestamp synchronization matters more than people realize. If your local clock drifts, the logs look fabricated. I use chronyd and include

timedatectl status
in every evidence archive.

For Asia-Pacific hosts I have seen better results with written demand letters before chargebacks. Regulators in Singapore and Japan respond faster than banks, in my limited experience.

conbini > datacenter snacks
12 #4

- the guide omits chain of custody entirely
- hash your logs immediately:

sha256sum *.log > manifest.sha256

- store hashes on a system you do not control. Email to yourself counts
- screenshots are trivially forged. Video with visible system clock is better
- for legal weight, notarized affidavits cost approximately $15 in most jurisdictions
- the partial refund outcome suggests weak documentation, not strong

-t

worst bandwidth, best stories
4 #5

Mas ⏰ tipo...

Nossa! Kkkk

#6

Which three public nodes do you use for iperf3

Post a reply

You need an account to reply. Log in or register to join the conversation.

Post reply Preview Save draft