4 ms·
Scaling One Million Checkboxes to 650M checks
- xivzgrev 2y agoNice write up - curious much did it end up costing?
- eieio 2y agoAh I should have included this (I'll edit the post shortly) Think the total cost was about $850, which was (almost) matched by donations. I made a mistake and never really spun down any infrastructure after moving to go, and also could have retired the second redis Replica I spun up; think I could have cut those costs in half if I had been focused on it. But given that donations were matching costs and there was so much else going on I wasn't super focused on that. I kept the infra up for a while after I shut down the site (to prepare graphs etc) which burned a little more money, so I'm slightly in the hole at this point but not in a major way.
- isoprophlex 2y agoI wonder what that would have cost you on Hetzner, for example. I have a dedicated 20 vCPU box with 64 GB of ram and a terabyte of SSD. Bandwidth is free... and all this for 40 eur/month. This should, especially after your Go rewrite, be enough to host everything?
- eieio 2y agoyou're right, I probably could have saved some money by using Hertzner! But I'm used to using Digital Ocean, and most of my projects haven't had these scaling problems, and I think changing my stack ahead of launching the project would have been a mistake. If I was planning to keep the site up for long I would have moved, but in this case I knew it was temporary and so toughing it out on DO seemed like a better choice.
- isoprophlex 2y agoHaha yeah of course, the click a button thing is super convenient. I recently had to rebuild my box because I left a postgres instance open on 5432 with admin:admin credentials, and without default firewalls in place it got owned immediately. That would have been less painful on DO for sure.
- eieio 2y agoYeah I think this was particularly handy for Redis - click a box to upgrade my Redis instance (or add a Replica) while maintaining data with full uptime was really really nice. Painful to use managed redis when I was debugging (let me log in! let me change stuff! give me the IP!! ahhhhh!!!!) but really nice otherwise. A little painful to think about giving that up, although I coulda run a really hefty redis setup on hertzner for very little money!
- whynotmaybe 2y agoAwesome ! Will your next post be a statistical analysis of which checkboxes' were the less/most checked ? I remember scrolling way down and being kind of sad that the one I choose was almost instantly unchecked.
- eieio 2y agoI’m gonna share the raw data soon! Just have one more story about the site I need to tell first.
- geek_at 2y agoIs the game still live? When I go to https://onemillioncheckboxes.com/ https://onemillioncheckboxes.com/ nothing is checked and in the JS console I just see {"total":0,"totalGold":0,"totalRed":0,"totalGreen":0,"totalPurple":0,"totalOrange":0,"recentlyChecked":false}
- kube-system 2y agoFrom TFA: > We passed 650 million before I sunset the site 2 weeks later.
- geek_at 2y agoAh thanks. Makes sense since the server costs were 800+$
- deleted 2y ago[deleted]
- xnx 2y ago> Building the site in two days with little regard for scale was a good choice. Probably the key takeaway that many early-career engineers need to learn. Scaling's not a problem until it's a problem. At that point, it's a good problem t have, and it's not as hard to fix as you might think anyway.
- hobs 2y agoAs long as you also took "so keep the system simple and basic" to heart as well - I have seen many systems where the obvious choice was microservices, not for scaling or team separation mind you, but because the devs felt like it. Scaling those systems is a total bitch.
- isoprophlex 2y agoTIL you can run Lua scripts on your Redis server. That's so nice, I never knew!
- jorl17 2y agoThis was a fantastic writeup!!! Congratulations on the website. To me, though, the writeup is what you should be most proud of!!
- eieio 2y agoThank you! I spent substantially more time on the writeup than I did on the site pre-launch, which is pretty funny to me
- adityaathalye 2y agoHah! Hard relate... Once or twice I've gotten side-tracked by the writing of, and ended up shipping a blog post about the code I was writing, before I finished the code itself.
- pizzafeelsright 2y agoMany lessons learned along with great historical knowledge of (distributed) systems. I think you hit every type of interruption and point of failure, except storage space, and it is great to see your resolutions. I wasn't aware Redis could do the Lua stuff which makes me very interested in using it as an alternative state. As for the bandwidth - one of my biggest gripes with cloud services as there is no hard limit to avoid billing overages.
- eieio 2y agoThank you! FWIW I certainly hit storage space in some boring ways - I didn't have a good logrotate setup so I almost ran out of disk, and I sent my box-check logs to Redis and had to set something up to offload old logs to disk to not break Redis. But neither of those were very big deals - pretty interesting to have a problem like this where storage just wasn't a meaningful problem! That's a new one for me. And yeah, thinking about bandwidth was such a headache. I was on edge for like 2 days, constantly checking outbound bytes on my nic and redoing the math - not having a hard cap is just really scary. And that's with Digital Ocean, which has pretty sane pricing! I haven't used the popular serverless stuff at all, but my understanding is that you get really gouged on bandwidth there. (also yes, lua-in-redis is really incredible and lets you skip sooo many hard/racey problems as long as you're ok with a little performance hit, it was a joy to work with)
- wonger_ 2y agoAs someone new to backend - is there a simple alternative architecture for this project? I hope there's an easier way to host a million bits of state and sync with clients. Some of the solutions in the post went over my head. Kudos to the author - your projects are great.
- isoprophlex 2y agoI don't think it gets much simpler than this to be honest... except for un-scalable things like keeping a single global list of a million booleans in the same process as your backend api.
- wild_egg 2y agoMaybe dumb question but why is keeping a million booleans in one process un-scalable? That's only 125KB of memory which can easily live inside CPU cache and be operated on atomically.
- eieio 2y ago(I'm the author) I don't think it's unscalable at all - it's just that if you do this there's not a great story for adding a second machine if the first one can't handle the load (but ofc a beefy machine with a fast implementation could handle a lot of load). When we did the go rewrite we considered just getting one beefier box and doing everything there (and maybe moving Redis state in memory), but it felt easier and safer to do a drop-in rewrite.
- alright2565 2y ago> there's not a great story for adding a second machine if the first one can't handle the load I mean this is basically your redis situation right? Just with a very specialized "redis". You could scale this out, even after the pretty massive ability to scale up is exceeded. Have some front-end servers that act as a connection pooler to your datastore. Or shard the datastore, and have clients only request from the shards that they are currently looking at.
- dang 2y agoRecent and related: One Million Checkboxes - https://news.ycombinator.com/item?id=40800869 https://news.ycombinator.com/item?id=40800869 - June 2024 (305 comments)
- butz 2y agoThis project won't be complete until it supports the elusive "indeterminate" state of the checkbox.
- layer8 2y agoIt should go indeterminate whenever clicks from two users on the same checkbox are detected where the second click occurred before that copy of the checkbox received the result of the first click.
- winrid 2y agoThese are fun projects. About six years ago I launched Pixmap on android, which is a little collaborative pixel editing app, supporting larger images (like 1024x1024 grids etc). I had a queue that would apply each event to png images, and then clients would load the initial PNG on connect, and then each pixel draw event is just one small object sent to the client. This way I could take advantage of image compression on initial load, and then the change sets are very small. Also, since each event is stored in a log, you can "rewind" the images [0]. [0] 22mb: https://blog.winricklabs.com/images/pixmap-rewind-demo.gif https://blog.winricklabs.com/images/pixmap-rewind-demo.gif
- usernamed7 2y agoNeat! I was exploring a similar idea about per-pixel updates to many web clients, but i found it would be way too bandwidth/storage intensive to do what I wanted to do. So I've been tinkering with canvases that can be addressed by API calls https://x.com/RussTheMagic/status/1816749136487588311 https://x.com/RussTheMagic/status/1816749136487588311
- winrid 2y agoI see what you're doing is submitting shapes over the wire. That's a bit different than what a pixel art application has to do, unless we were doing like color fill and stuff, which it doesn't support. Every pixel you draw it shows your name next to the square, too, so it's not like "draw a shape and submit" kinda thing. regarding storage of the log, compression is a thing :)
- usernamed7 2y agoFor sure, different projects - what I was doing when i started, expressing individual pixel updates was a huge storage hog, as trying to draw the most rudimentary shapes resulted in quite large storage (even after gzip) - and would translate to large bandwidth requirements (as I was going for realtime). I moved over to canvas drawings because I could express rendering with much more expressive syntax.
- junon 2y agoReally cool, awesome followup to the original project.
- j0hnyl 2y agoWould you be willing to share your nginx config?
- creativenolo 2y ago> This also validated my belief that people are hungry for constrained anonymous interactions with strangers.
- huem0n 2y agoHere's the opposite of your scalable implementation: 1mil checkboxes in under 1000 characters! (Deno) https://gist.github.com/jeff-hykin/4cdebafd8698298d021f103e22a2b98a https://gist.github.com/jeff-hykin/4cdebafd8698298d021f103e2...