Hacker News Reader

Comment by maxpert | Hacker News Reader

Good to hear you like it. Server is written to be lightweight and keeping things simple helped a lot. NodeJS totally sucked memory, Golang helped a lot in that perspective.

View on HN

Got server load averages? how much ram is used?

1K parallel connections were handled under 100MB of memory. 2K were around 150MB

50KB/connection and 50MB fixed cost?!!?

Nops nothing is fixed it's just one scenario, besides your math is wrong. 50KB/connection won't map to 2000 connections.

(rate of) change in memory per user

    150MB    - 100MB
    -------------------  =  50KB/user
    2k users - 1k users

no?

if 0 -> 1000 users is 100MB, how can you explain 1000 -> 2000 with 150MB

Fixed cost: 50 MB

Variable Cost: 50KB/user

50 + 1000 * (0.05) => 100 MB

50 + 2000 * (0.05) => 150 MB

Pretty straightforward?

Well if that's the math that works for you, but I won't assume anything here. If I would have written it in C or Rust lang I would have given quoted a more deterministic memory usage. Bottom line, benchmarks just quoted numbers. Should have put up a Notice disclaimer in comment as well.

Reply on news.ycombinator.com