pull down to refresh
27 sats \ 5 replies \ @k00b 17h \ on: What creative ideas have you been rambling on? Design
I'm mostly bug hunting. The closest thing to something creative I've been thinking about is how to add incremental aggregate statistics to the micropayment engine. Currently we do periodic refreshes over recent time ranges, but that creates lag in the aggregate values that I find inelegant (and people get confused about them).
Thinking something like running timescale in parallel and query that on the fly?
reply
I find framework/tool/infrastructure additions to be more trouble than they're worth at SN's scale.1
We currently construct time buckets of stats in a normal table. Instead of continuously refreshing those time buckets, I'm thinking of doing some kind of incremental update atomic with a payment's state transitions.
Footnotes
-
my general vibe is to abuse what we have (frameworks/abstractions/whatever) until they can't do the job anymore ↩
reply
my general vibe is to abuse what we have (frameworks/abstractions/whatever) until they can't do the job anymore ↩
I think this is the way to go in general, even beyond your scale. New systems can be such a can of worms and should only be added with great care (of course there are exceptions)
reply
Bug hunting could be fun too. Have you tried giving yourself a prize every time you find or fix one?
add incremental aggregate statistics to the micropayment engine.
Tricky I guess, and totally out of my comfort zone because not sure what incremental aggregates refers too. Data? is the lag created because the time ranges are fixed to begin with? Or could it start from
now() and go backward instead?reply
Bug hunting could be fun too
Indeed
reply