Sharing what worked on our test world this week.
Environment: Ubuntu 22.04, 4 vCPU, 8GB RAM, MariaDB 10.11.
We logged query times over 200ms on market browse during peak hour.
Has anyone stress-tested this with 200+ CCU?
---
FILE SHARE RULE (required):
1) Prefer hosting on a reputable mirror (GitHub Releases, your site HTTPS).
2) Every download link MUST include a VirusTotal analysis URL for that exact file hash.
3) Paste: file name, version, SHA-256, VirusTotal link, supported client/engine, license.
4) Archives without a VirusTotal link will be removed.
Example VT link format: https://www.virustotal.com/gui/file/<sha256>
Synthetic example package: ots-community-tool-8221.zip
SHA-256: 6f74732d73796e7468657469632d66696c652d383232302d6f70656e54696269
VirusTotal: https://www.virustotal.com/gui/file/6f74732d73796e7468657469632d66696c652d383232302d6f70656e54696269
Note: demo hash for seed content only — replace with your real release hash before publishing.
Looking for feedback on imbuement mockups (#8221)
Started by ProtocolFox - 8/13/2026, 5:13:39 AM - 3 replies
Thanks — we saw the same spike when market history grew past 500k rows. Also: please keep the VirusTotal link next to the mirror. Example: https://www.virustotal.com/gui/file/6f74732d73796e7468657469632d66696c652d383232302d6f70656e54696269
Agree on the VirusTotal rule for binaries. Hash + VT link or it does not ship.
If you share the stacktrace (redact IPs), I can compare with our build.
Post a reply
Posting as Member