trebecks

5 ms·

1.
by trebecks 2y ago
yeah i like this model. then you can use whatever synchronization junk you prefer to share state between the threads, if you have any. your library looks well written and clean. thanks for sharing. if anyone else wants to go coroutine spelu
2.
by trebecks 2y ago
the scheduler is probably simpler if coroutines can't bounce between cores. you can have a single thread per core that runs the scheduler to multiplex a bunch of coroutines on the single thread, which lines up with the example linked i
3.
by trebecks 2y ago
i got caught up on that statement too. i interpreted it as they can spin up more servers with their own volumes but thats not really 1 ebs volume anymore. maybe at their current load they only need 1? the op mentioned copying stuff to s3 at
4.
by trebecks 2y ago
if i'm reading the op right, they kind of use ebs as a buffer for fresh data until it ages out to s3. they use a "local" disk to hold the stuff used by the queries that people actually make and the queries run quick. they let
5.
by trebecks 3y ago
yeesh i didnt realize there was a patent on that. your link lines up with the authors predictions of cdns coming up with and patenting different ways to accomplish this. i guess it makes sense and maybe it isn't a bad thing, but i neve
6.
by trebecks 3y ago
the "Stupid DNS Tricks" section says using dns to map clients to a nearby pop is a trick. they predicted this trick would be used for decades and it seems like they were right. i know cloudfront uses this in some fancy form. i don
7.
by trebecks 3y ago
the SHED_LOAD thing offered by ns1 looks cool. anyone have experience with it? https://help.ns1.com/hc/en-us/articles/360020683413-Configur... . seems like something juicy missing from route53. ns1 even has an
8.
by trebecks 4y ago
some nyc bridges and tunnels charge both ways. for the bridges and tunnels connecting ny and nj, you only need to pay going nj -> ny.
9.
by trebecks 4y ago
i use https://github.com/giltene/wrk2 pretty regularly. it has decent lua hooks to customize behavior but i use it in the dumbest way possible to hammer a server at a fixed rate with the same payload over and over. i r
10.
by trebecks 5y ago
flink uses akka for control plane kind of stuff. data plane stuff, like piping data between tasks, doesn't. check out https://flink.apache.org/2019/06/05/flink-network-stack.html for some (maybe outdate
11.
by trebecks 5y ago
nginx too http://nginx.org/en/docs/stream/ngx_stream_proxy_module.html
12.
by trebecks 6y ago
yeah, that is what refresh tokens are used for and it works well for access tokens with a short ttl. in practice i have seen access tokens with ttl of a few hours. i think it might be done to cut down on the refresh calls? in that case, if
13.
by trebecks 7y ago
the user isn't signing anything. the server is signing something it sends to the user. when the user sends it back to the server, the server checks the sig to make sure the user didn't alter/forge it.