Viewing profile — arynda
arynda
HN member- Joined
- Mon, Sep 12, 2022, 4:40 PM UTC
- HN karma
- 34
- Public activity
- 22 items
- HN profile
- View on Hacker News ↗
About arynda
No profile information was provided.
Recent public activity
- comment
-
comment
Comment #36612525
[dead]
- comment
-
comment
Comment #36606965
[dead]
- comment
-
comment
Comment #35323375
If you want an actual startup-oriented bank that has their shit together (e.g. they employ sweep accounts and by default you have $5M of FDIC insurance), mercury.com has been excel…
- comment
-
comment
Comment #35299807
I miss Topcoder. Funny story I went back through all my old SRMs and found one where I was placed in the same room with none other than mzuckerberg. He even unsuccessfully challeng…
- comment
- comment
- comment
- comment
- comment
-
comment
Comment #34698997
any chance you have a link to a good readme on setting up single-node docker swarm?
-
comment
Comment #33769543
> ClickHouse performs what is known as PREWHERE processing > p.s. Scans are ridiculously fast. Good point, I should have mentioned this was basically a worst-case scenario for Clic…
-
comment
Comment #33769374
Not in particular sorry, most of the good content I've found is on Altinity [1] and Alibaba's technical blogs [2][3]. These tend to be mostly focused on how the data itself is stor…
-
comment
Comment #33769226
Comparison on Clickhouse, also runs in about 30-40ms, however there's no indexing being used and this is a full-table scan. create table if not exists test_table ( id UInt64, text1…
- comment
-
comment
Comment #33354429
The same way a spoken language is a communication tool and doesn't restrict what is discussed.
-
comment
Comment #32815975
https://asciiflow.com/
-
comment
Comment #32813618
That's cool. I've been thinking through a similar design. Would this be an accurate description of your approach? queues hold jobs, the scheduler/dispatcher handles load-balancing …
-
comment
Comment #32812901
How did you end up solving the rate limiting? Were the workers themselves responsible for coordination via a semaphore (e.g. there's already 25 of us, don't consume from this queue…