Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
chucky_z
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
36 ms
·
391.
▲
by
chucky_z
10y ago
This is one of the few emulators that will run _well_ below the suggest specifications. I've played it on much older hardware with a very low end GPU, and it runs quite well (depending on the game, of course.)
392.
▲
by
chucky_z
10y ago
What are the pros/cons of doing this in HAProxy natively? Could you just use something like a health-check on a cluster system like zookeeper/etcd/consul/keepalived/... to simply peek at the lag time, and then mark
393.
▲
by
chucky_z
10y ago
Interesting. I live in the south bay right next to the Cisco campus, and the amount of new employees they are hiring is staggering. I wonder how many of the 14,000 are being rehired as a contractor or something?
394.
▲
by
chucky_z
10y ago
At a previous company I worked I worked at there was a table that maxed out postgresql's column limit. That did not need to be that wide. It was much better suited as a ~30 column table with a single hstore column (does the key exist
395.
▲
by
chucky_z
10y ago
Yes, I've used Terraform since 0.3. I feel strongly about two things: 1) I screwed up at the beginning so hard (there were _no_ best practices to be found so it was a bit wild west) that I've come to the point where I need to use
396.
▲
by
chucky_z
10y ago
> the response will probably be silence (rarely flaming, just silence). This is my favorite part of the Linux community. Ask something that you aren't sure of, and if it's wrong, you'll get quite some volume of responses
397.
▲
by
chucky_z
10y ago
In for instance, a bioscience lab, I don't believe that results should even be accepted unless they're repeated with similar reagents. Some reagents are so specific they only prove something.... for that one single thing, which
398.
▲
by
chucky_z
10y ago
Did you read this? https://www.postgresql.org/docs/current/static/high-availabi... I'm not sure what more you can ask from documentation. Does MySQL document Vitess, Galera, MaxScale, etc...?
399.
▲
by
chucky_z
10y ago
What replication issues are you referring too? I never once had a problem with pgsql's replication across 8.1->9.5. It would randomly die, but that was always either my fault or the applications fault, never pgsql itself. The lack
400.
▲
by
chucky_z
10y ago
online schema change is absolutely riddled with crippling bugs if you use foreign keys. Just a heads up, we've had to basically take everything it does and make an in-house version. The idea and execution are great, when it actuall
401.
▲
by
chucky_z
10y ago
From my experience, the problem is not how does any NoSQL solution stand up vs. any other NoSQL solution. The question to ask is "What caveats affect me the least?" and then go with that NoSQL solution. In the case of MongoDB,
402.
▲
by
chucky_z
10y ago
I will argue _against_ MongoDB all day, but there is most certainly a time and place for it. If you have a real firehose of data, don't care too much about the accurateness, and really need good speed... MongoDB is not an awful choice
403.
▲
by
chucky_z
10y ago
Regarding variable precedence, it's pretty simple to grok in 2.x+, and well-documented now (it was a serious nightmare, and a very valid complaint... but isn't as much anymore). For sharing common group_vars, what I do is my inv
404.
▲
by
chucky_z
10y ago
That's roughly 4k qps. Assuming it's a lightweight API a single server isn't out of the question. Nginx will handle 20k qps until the end of time on a tiny box serving static content.
405.
▲
by
chucky_z
10y ago
The article only mentions their app. I try to install as few apps as possible for personal reasons. Their mobile web UX is turning sour, fast. (I primarily used the messenger function, so my view is very skewed the) I don't have any s
406.
▲
by
chucky_z
10y ago
My response to the comment for triggers and PGSQL would be: Postgres tries its best to stop you shooting yourself in the foot. Similar to the top comment, all the real problems I've ever encountered with postgres (heck, all major RDB
407.
▲
by
chucky_z
10y ago
I use Ansible to do all of the CIS recommendations. Took about a day and following along with the CIS guide to do it.
408.
▲
by
chucky_z
10y ago
I was simply disagreeing with the title of "SELinux is beyond saving." SELinux doesn't need saving for those who have a strong use-case. There are some great lesser alternatives like AppArmor, grsec, TOMOYO, and AKARI if
409.
▲
by
chucky_z
10y ago
May I disagree partially, using this authors exact words? "... Unless you are a high risk target, spending almost any time beating SELinux into shape on your machine is a bad tradeoff and pretty much a waste ..." -- https:/&
410.
▲
by
chucky_z
10y ago
Everyone should try PostgreSQL with hstore (and JSONB now, too!). This is a key/value store inside an RDBMS that just works, and it works great! I converted a crappy sloppy super messy 1000+ column main table in a ~800GB database to u
411.
▲
by
chucky_z
10y ago
Postgres scales great up to 256gb, at least with 9.4. After that it'll use it, but there's no real benefit. I don't know about MySQL. SQL Server scales linearly with memory even up to and past the 1TB point. I did encount
412.
▲
by
chucky_z
10y ago
I've confirmed this... It's an opt-out proxy in this situation (can be setup as opt-in). https://crypto.stanford.edu/flashproxy/ > There is an options page[1] (the same page you get by clicking on the bad
413.
▲
by
chucky_z
11y ago
Interesting you mention awk. Do you use that professionally? For string manipulation I use almost exclusively pipe output to bash then format/grok with awk/sed, and wish that more (any?) languages implemented them fully!
414.
▲
by
chucky_z
11y ago
A real announcement (unicode support) in an April Fool's package (doing the announcement only mentioning emoji). LukeShu nailed it with their reply. :)
415.
▲
by
chucky_z
11y ago
Interesting there seems to be a shift in the 0-2 year job length position. I wonder if this is because the common trend is to jump ship at 2 yrs, so folks are going out job hunting, and getting a competitive raise at their current position
416.
▲
by
chucky_z
11y ago
We have a backend position (primarily PHP) open at our company (am I allowed to pimp that outside the who's hiring thread?). It's been open for ~6 months or so now, and haven't had a single female applicant. Not, we haven&#
417.
▲
by
chucky_z
11y ago
People pay for RHEL, SUSE, Windows, Mongo, MySQL, etc.. support even though they may be part of a company perfectly capable of resolving any issue with the software. You get more than just basic support with all of these contracts. =)
418.
▲
by
chucky_z
11y ago
Our indexes are probably very small (about 40gb total) but I've found if you value speed and consistency over all else.... just run a single, 1 shard node and have a fallback in case of random errors. I just do major version upgrades
419.
▲
by
chucky_z
11y ago
As a consumer of AWS's services, every time I start to think "I could really use this service..." or I have a "If AWS had this..." thought, they seem to release something that addresses this concern. If they added
420.
▲
by
chucky_z
11y ago
Isn't the whole point of a devops individual/team to reduce friction to "... break down barriers, increase automation, bring collaboration and iterate."? I understand that there should be company buy-in and individuals c
More ›