Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dan353hehe
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
91.
▲
Kafka cluster auto healing and workload balancing
(github.com)
1 points
by
dan353hehe
9y ago
|
0 comments
92.
▲
by
dan353hehe
10y ago
about year ago I was working in the illumos kernel codebase and was using sublime. It seemed to work well enough for what I was using it for, still was a bit hard to find the appropriate file quick enough though.
93.
▲
by
dan353hehe
10y ago
Right and I agree. however I'm sure that most of the APK would be images, etc. and not the actual executable.
94.
▲
by
dan353hehe
10y ago
what sort of hardware are you using? and how would shrinking the app to 64k save your team a considerable amount of money?
95.
▲
by
dan353hehe
10y ago
Fitting in the cache is important for high performance applications. I do agree that in resource constrained environments it is good to examine what it taking up space, but the exe may not be the first place to look, especially for image he
96.
▲
by
dan353hehe
10y ago
That makes sense. if the hot code path in your executable can't all be in the cache at the same time then it will have a performance penalty.
97.
▲
by
dan353hehe
10y ago
I'm just a little confused, With terabytes of disk and gigabytes of ram, why should someone spend time shrinking the size of a binary down? I understand if you are working in an environment where both of those could be limited such a t
98.
▲
by
dan353hehe
10y ago
> They talk about master nodes and slave nodes, while at the same moment claiming that there is no SPOF. If I remember right (its been a while), the master and slave nodes mentioned are just in the manager which is control of the ring. E
99.
▲
by
dan353hehe
10y ago
the linked repo doesn't really contain all the erlang code. its mostly designed to pull and build the actual projects. hence the "Shell code"
100.
▲
by
dan353hehe
10y ago
I remember evaluating this project several years ago, (maybe 2 or 3?) as a possible S3 replacement, and it actually worked fairly well. We ended up not using it as our requirements changed. Yosuke Hara the main developer on the project was
101.
▲
by
dan353hehe
11y ago
I don't think I have ever heard anyone say "juvenile foible of nostalgia" before in my life. I have generally found that when people become art critics and try to describe why the like/don't like a certain piece, it
102.
▲
by
dan353hehe
11y ago
This reminds me a bit about what was mentioned in the book "good to great". A company, or in this case a product, can do everything at a level a little above garbage, or it can focus on its core competencies and be the best at som
103.
▲
Nil pointers and receivers in go
(play.golang.org)
1 points
by
dan353hehe
11y ago
|
0 comments
104.
▲
by
dan353hehe
11y ago
seesaw is just a management layer on top of ipvs (or lvs).
105.
▲
by
dan353hehe
11y ago
The third link that you posted is for keepalived. keepalived uses LVS as the actual load balancer (which is what seesaw uses as well). So as long as you can setup seesaw to run a few scripts to inform DisitalOcean which droplet currently ha
106.
▲
by
dan353hehe
11y ago
True it is, however to use manatee you have to build on ZFS, which unfortunately is not as widely adopted as it should be.
107.
▲
by
dan353hehe
11y ago
Thats true, however in yokes case, each cluster needs a third member called a monitor who only serves to resolve network partitions. a secondary cannot self promote to primary without the monitor agreeing. two node systems can never work as
108.
▲
by
dan353hehe
11y ago
sustained writes of several hundred thousand, with a 25x decrease in database size?! I knew it was the future today when I woke up.