Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mmt
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
19 ms
·
151.
▲
by
mmt
8y ago
If mainframe reliability is what it is purported to be, then, for someone making this choice as an alternative to a mainframe, especially if they've been on it for decades already, it's a very solid reason. It is, of course, only
152.
▲
by
mmt
8y ago
To be fair, the overall context of the conversation isn't (all) "other operating systems" but, specifically, mainframe ones. Additionally, the GP referenced "the past few decades", which certainly includes 5 years a
153.
▲
by
mmt
8y ago
> From my point of view for typical modern bussiness workloads that necessiate large machines (ie. SQL RDBMS or something similar) only thing that you really care about is memory size. That's my general impression, as well, but I ha
154.
▲
by
mmt
8y ago
How does this map to the current state of commodity computing? For example, it seems we already achieved that with disks, once embedded controllers attached to DMA-capabled HBAs became the norm. A similar thing seems to have happened with N
155.
▲
by
mmt
8y ago
> They're still cheaper Are they, though? Commodity hardware certainly is, but it's not as if cloud providers are charging a small margin on top of that. They're charging a multiple, potentially as large as 10x. Combined w
156.
▲
by
mmt
8y ago
> no data theft or any malware destroying data. That would only be true if the mainframes never interfaced to any other systems or to any humans. Since the latter can't be the case, and the former hasn't been the case for a lon
157.
▲
by
mmt
8y ago
> On the other hand, you can get rack-mount x86 server with several TB of RAM for fraction of price of mainframe which is exactly the hardware for new applications that would otherwise be best served by mainframe. I expect the largest on
158.
▲
by
mmt
8y ago
If speaking very roughtly, I'd go so far as to extend that analogy to the CPUs, as well, and, more importantly, the I/O.
159.
▲
by
mmt
8y ago
Although downvotes don't necessarily mean factual incorrectness (and I didn't downvote), that may have been the case here. It may also have been because the comment could be read as implying undue influence (and thereby indirect s
160.
▲
by
mmt
8y ago
> why wouldn't I want to use something horizontally scalable instead? Besides the (purported) reliability reasons other commenters have brought up, because "vertical" [0] scalability is, often enough, more efficient in ter
161.
▲
by
mmt
8y ago
2 weeks seems like an outlier. A recent thread [1] described someone getting cash from an ATM via bitcoin in 20 minutes. One of the comments theorized that this was because the ATM service used only 2 verifications instead of 6, taking a sl
162.
▲
by
mmt
8y ago
> They are buying more bandwidth so they can get it cheaper. I don't think that's actually true. The first assumption, that they are buying something from someone else is potentially flawed, and the conclusion is based on anoth
163.
▲
by
mmt
8y ago
> Bitcoin Layer 1 (on chain) ~= .09 euro That's the same OOM as what one might expect from a traditional payment card processor (although I don't think it's ever a flat fee, but that's less relevant in the context of
164.
▲
by
mmt
8y ago
One that actually works, with sufficient trust, still has "a middleman" (blockchain solutions implement this as many, distributed middlemen, IIUC, but that detail seems immaterial to an end user) and thereby still requires a "
165.
▲
by
mmt
8y ago
> I’ve come to think that people should just start with Postgres and only pick something else if Postgres doesn’t work out Even that standard results in people giving up on PG too early. It's possible to get it to continue working o
166.
▲
by
mmt
8y ago
> I would argue that any Linux or vSphere admin with any real amount of experience should be able to read any of the documentation I linked and be able to confidently work through it in an hour or two. Having glanced through those docume
167.
▲
by
mmt
8y ago
I recently interviewed at a startup that explicitly uses both, with PG being something of an authoritative backend store that feeds into ES as the primary frontend store (since the frontend is search-heavy). It might be possible to get it
168.
▲
by
mmt
8y ago
Sometimes the issue with a comment isn't about its truth or lack therefore, but with its tone or potential for inciting flamewar (a.k.a. trollishness). With a brand new account, the intent is even harder to discern. > PostgreSQL sti
169.
▲
by
mmt
8y ago
It can be at least partially explained by a mismatch between the "cloud" model and the underlying engineering (and market) reality [1]. One has to build (or buy) for peak bandwidth. Selling it pay-as-you-go, with no regard to loca
170.
▲
by
mmt
8y ago
> By no means do you need DPDK to basically eliminate the latency difference I didn't mean to imply that was your argument. > I just wanted to point out how low latency can go in general. Rather, I meant that "can" isn
171.
▲
by
mmt
8y ago
> But truth be told, not having to deal with servers at all is magical. And if your team is used to it, it does cut down on a lot of worry such as patching stuff. Spectre or Meltdown patches? Ha, zero effort for us. The problem with this
172.
▲
by
mmt
8y ago
With potentially substantial engineering effort, including needing to hire someone with a relatively rare expertise, they could [1] eliminate that specific downside of virtualization. However, there are remaining overhead/downsides, an
173.
▲
by
mmt
8y ago
> It should come as no surprise the CBP will cooperate with other government departments, i.e. ICE Considering the "C" in both agency acronyms stands for the same thing, it would be more surprising if they didn't work very
174.
▲
by
mmt
8y ago
> Not sure why you'd compare Houston to all of California? I believe everyone in this sub-thread has used "CA" to mean the SF Bay Area plus greater Los Angeles (and certainly I have). Similary, "NE" was just shor
175.
▲
by
mmt
8y ago
This may be attributable less to a lack of enthusiasm and more to the physical size and TDP of Epyc CPUs. Additionally, it would be very hard to take advantage of Epyc's increased PCIe lane count at half-U densities (which is, of cours
176.
▲
by
mmt
8y ago
> Are the 128 lanes per system a feature that actually draws in users with real world demands or is this the wrong thing to focus on? I'm going to go out on a limb and suggest (based on my own experience[1]) that most users are too
177.
▲
by
mmt
8y ago
Unfortunately, higher temperature says less about power and more about thermal design (often of the overall system and not just the chip). > On paper, you get more lanes at a lower TDP w/ AMD. I was hoping you (or anyone) had at lea
178.
▲
by
mmt
8y ago
> The PCIe lane story is stuff of fanboys. It comes at a cost, power and heat. Could you unpack this a bit? Specifically, I'm curious if the cost is a premium per lane (e.g. W/lane greater on AMD than on Intel) [1]. Also, is th
179.
▲
by
mmt
8y ago
> Look at all big companies (and not just the recent Internet ones of the last 20 years), and look at where they have sites. Jobs in most of these places. But how many of those jobs are technical/programming (in those places)? Even
180.
▲
Importing Data the WTF Way (2009)
(thedailywtf.com)
1 points
by
mmt
8y ago
|
0 comments
More ›