HN user

jordo

72 karma
Posts1
Comments19
View on HN

REALLY looking forward to trying this. Mixpanel has the most obscure pricing model of any SAAS i've ever tried to integrate with... When we 'upgraded' from their free tier to a paid tier we were DOWNGRADED from 20M events a month to 10K events a month. Does that make any sense??? They talk about 'transparent and easy to understand pricing', but immediately after I upgraded to a paid plan we were downgraded from 20M events to 10K events.

We actually immediately cancelled our paid plan and went back to their free tier. To match what they provide in their free tier (20M events), the cost is $2,289 USD / month (no thanks). https://mixpanel.com/pricing/plan-builder/?dcv=growth

So basically we can either pay $2,289 USD / month, or pay nothing, and still get the same number of tracked events. Just bizzare... We've moved on, and I've been on the search for an alternative ever since.

We made https://rocketbotroyale.winterpixel.io in godot 3.5. ~ 20MB wasm binary, ~20MB game assets. We did however, have to do a ** ton of engine modifications to get the performance characteristics we needed on web, so mileage may vary depending on what you are actually building. But overall, 3.5 supports web very well. 4.0 is too unstable for us to use it yet, so jury still out on that one.

But the absolute, most amazing thing ( coming from the anxiety of app 'submissions', going through 'reviews', etc ), is the ability to update/fix/hotpatch everything instantly. Like within seconds. We have a simple CI/CD workflow that builds, updates & deploys a new godot site ( with dedicated gameserver backends) within seconds. The ability to just do this however you want, whenever you want, without going through some kind of platform distribution interface is great. With the exception of WGSL being such a dumpster fire of a spec, I'm pretty bullish on web for gamedev & distribution. There's some really great stuff being built right now, see: wasm+webtransport+wgpu

I always think of the Monty Hall problem with 100 doors. And with the game show host revealing 98 'goat' doors thus leaving two doors left (the original guess, and another one). You'd switch then right? :)

Linux Kernel 5.14 5 years ago

This is EXACTLY the issue we are currently running into while hosting our gameservers on kubernetes via agones https://agones.dev/site/. While our gameserver processes don't really need a full core, they do need to be scheduled regularly to meet their tick simulation deadlines. A gameserver that ticks at 60hz absolutely needs CPU time at the very least every few milliseconds. Not getting scheduled back in time for a game tick means more input latency, and wreaks havoc on game clients trying to adjust their prediction buffers to optimally time their input receipt server side before the next server tick.

Bad, bad, bad scenario all around. A gameserver process really needs to get scheduled like a heartbeat. Ticks can't be late on the server as it really screws everything else up big time. We've seen these "bursting" effects really start to take it's toll, to the effect that we're now just setting a request and limit of 1CPU for each game server process (even though we could pack a lot more punch here).

This is exactly why we are using DigitalOcean to host our gameservers... Our egress costs are basically 1/10th of what we would pay on the big three.

DigitalOcean Egress - $0.01/GB

This. Same sentiment here. Although one of the greatest strengths in the engine is the fact that it's open source, and extremely easy to build.

Any limitation I've come across I've been able to modify or extend with relative ease.