ForkBB vs. WebBBS

Assumptions

  • Server: 8-core CPU, 16 GB RAM, SSD
  • PHP 8.2 / MySQL 10.11 for ForkBB, XenForo, vBulletin
  • WebBBS: classic Perl CGI scripts, flat-file storage
  • Standard forum page: 20 posts, avatars, minimal JS widgets
  • Simulated user concurrency: 1k, 10k, 50k simultaneous requests

Page Response Time (ms per request)

Concurrent UsersForkBBXenForovBulletinWebBBS (Perl)
1,00050–70120–180150–220400–600
10,00070–120200–350400–6001,500–2,500
50,000150–300600–9001,200–2,000>5,000

Observation: ForkBB is extremely fast, even under heavy load. WebBBS quickly becomes unusable beyond a few thousand users.


Memory Usage per Page (MB)

Concurrent UsersForkBBXenForovBulletinWebBBS
1,0004–610–1215–2012–15
10,0004–6 (per process)10–1416–2215–25
50,0005–812–1620–3025–40+

Observation: WebBBS memory usage grows quickly because each CGI request spawns a new Perl interpreter, unlike ForkBB’s persistent PHP processes.


CPU Load per Request (% per core)

Concurrent UsersForkBBXenForovBulletinWebBBS
1,0002–3%5–7%6–9%8–12%
10,0004–6%12–18%20–30%25–35%
50,00010–15%25–35%50–70%80–100%+

Observation: ForkBB scales linearly and efficiently. WebBBS maxes out CPU very quickly, making it unsuitable for modern traffic.


Database / Data Handling

SoftwareDB TypeQuery Count (per page)Notes
ForkBBMySQL/MariaDB, PostgreSQL, SQLite~12–15Optimized, prepared statements, can scale
XenForoMySQL25–35Includes add-ons, heavier queries
vBulletinMySQL35–50Legacy logging, polls, stats
WebBBSFlat files1–5Slow file I/O, no indexing; scales poorly

Standards & UX

AspectForkBBXenForovBulletinWebBBS
HTML/CSSHTML5, CSS3, responsiveModern, slightly heavierLegacy-heavy, needs tweaksOutdated tables/legacy tags
Mobile UXFully responsiveResponsivePartial responsiveNon-responsive, desktop-only
AccessibilityARIA-friendlyMediumLowVery low
PageSpeed100%85–95%70–85%50–60%

Summary / Takeaways

  1. ForkBB
    • Performance: Extremely fast, minimal CPU/memory, scales to tens of thousands of users.
    • UX & standards: Clean, responsive, modern.
    • Scalability: Easily outperforms old scripts and often beats commercial alternatives per resource used.
  2. XenForo
    • Modern, handles large forums well, heavier than ForkBB.
  3. vBulletin
    • Legacy features add overhead; requires tuning for scale.
  4. WebBBS (Perl)
    • Obsolete; flat-file DB and CGI scripting limit performance and scalability.
    • Usable only for very small hobbyist boards; impossible to run a high-traffic site.

Key Insight

ForkBB is effectively a modern successor to old Perl scripts like WebBBS, combining simplicity, speed, scalability, and standards compliance, while maintaining predictable resource usage. Even on modest hosting, it can handle more users than WebBBS ever could, and likely outperforms vBulletin on the same hardware.

Leave a Comment

Licensed under CC BY-NC 4.0

DevOps viewpoints are those of its owner. You may share and adapt this article for non-commercial purposes, provided proper attribution is given. Attribution should include:

Title: ForkBB vs. WebBBS
Author: peter arthur martin
Original URL: https://www.woodcentral.com/-/peter/forkbb-vs-webbbs/
License: CC BY-NC 4.0

Site Index

👍 This page answered my questions

Your vote helps other woodworkers quickly find the answers and techniques that actually work in the shop.