Did IBM Just Preview the Future of Caches?
anandtech.com
anandtech.com
In this new chip the L2 replaces the prior L2 and L3.
Edit: similar deal for Z14 4MB/4MB L2 + 256MB eDRAM L3.
In this case, and assuming that the package is thermally limited, there's no real reason not to go to a smaller die. Even if a 16 core, 512MB cache monster fit on reticle, if there's not much performance gap between that and the actual dual 8 core, 256MB cache system, why not take a yield gain from smaller dice?
If this is the case, I'd expect this die to be way smaller than the Z15 processor... < 400 mm^2? Anyone have numbers?
[1]: https://wccftech.com/ibm-z-next-gen-processor-detailed-telum...
According to the video presentation [1] each processor also contains an AI accelerator with more than 1000 compute engines for >6 TFlops
[1] https://www.ibm.com/blogs/systems/ibm-telum-processor-the-ne...
Completely tangential rant:
I just saw a tweet of a guy serving 200k connections on a $5 USD instance. I believe it because I've experienced it first hand several times. Serving static pages in 2021 is not a big deal, at all.
On the other hand, this is anandtech, a huge site that's been going on for years (decades?). For sure they get a lot of traffic, but I doubt they get something like 1M+ simultaneous requests per second. Can't they just solve this problem already? Whoever is in charge of their tech stack is hardly doing its job, this is unexcusable.
The NY Times does this for election day results because they fully expect that to get hit hard. They re-publish a static page every few minutes
And the funniest part of that story: the mainframes where so heavy they couldn't fit the existing server room, so they were parked for months in a warehouse, unplugged, waiting for some new dedicated server room to be built. (I don't know if the said server was eventually built or not, and if the mainframes were actually used or not in the end).
I visited the “server room” of the organisation responsible for e-healthcare(the software application that was in use by all public hospitals, doctors, and pharmacies in one state of India) as a consultant to learn the following.
Their server room is in an old repurposed residential building on the second floor!
The only ways to get there were either through narrow winding steps, or an ancient metal elevator that creaks and is also made for tiny humans.
IBM managed to sell two Mainframes(Z10) to run their Java apps. The mainframes could not be brought in because of the elevator problem. I kid you not, they brought welders on site to dismantle the racks, and then weld them back again inside the “server room”!
Cooling for the “server room” with two mainframes you ask? A few airconditioners that you’d typically installed at home and a table fan(I don’t know why it was there).
They were concerned about performance issues on their Java applications which were simply “JVM runs out of memory about every day”.
I luckily could bail out of that nightmare and escaped the whole situation.
I could only think about the govt employees who were in charge of purchasing that got to go on fancy vacations paid for by IBM. I obviously don’t know if it’s the case, but my own amusing speculation to explain the irrational purchase.
But even it was really down it wont be their first time with capacity problem. Unlike ServeTheHome where they host and even assemble their own Server, I think Anandtech's team are now simply a content writer with Future Publishing handling everything on the hosting and software side along with Ads.
But yes I think there is something very wrong with current trend of Web Development.
We had it really good when he was in charge. In depth technical dives from a curious position. https://imgur.com/a/MFAypUc
I believe Phronix is still good. https://www.phoronix.com/scan.php?page=home
ArsTechnica has waned and waxed over time. But they have always been solid-enough for me. They have always been up to defend the individual in technology policy and how trends in law enforcement deceptively catches up. They can get squirrelly with the climate view once in a while. BUT even if you disagree with them -- you can bet if you sincerely read their content they stance is well grounded.
As a stable and long term aggregator for open source and similar news and articles I have been very happy with lxer. http://lxer.com/
We're not an independent site anymore, so we have little control over how the site works and integrates into Future's back end (to be fair, compared to TH, we're not that integrated several years later because of a custom CMS and hosting setup, but it means Future won't put any $$$ into it until we transfer over).
Simply put, with the big publishers, writers are writers, publishers deal with the publishing.
I know we're not supposed to entertain this on HN, I think this would make a good 'Ask HN' - let me know if you make one.
> I just saw a tweet of a guy serving 200k connections on a $5 USD instance. I believe it because I've experienced it first hand several times. Serving static pages in 2021 is not a big deal, at all.
You can do that on a $1/month instance if you are clever about it. It's all about static serving.
Heavy load is something that can be detected and handled - if you're maxing out your CPU/network, switch to low-res/quality images, minimal CSS and do away with comments/recommendations. You could get that page down to 20kB and be mostly the same.
> Can't they just solve this problem already? Whoever is in charge of their tech stack is hardly doing its job, this is unexcusable.
A text+images news website should not be having this much trouble, it's embarrassing. That said, I'm sure there is something we do not understand - I would for sure like to speak with somebody from the site to understand it more.
Several times over the course of like an hour. It was a mmesage from Cloudflare, saying that your site took a long time to reply.
(At a previous employer, we got a tour of the data center where, along with racks and racks of commodity Linux servers, there was also an IBM mainframe. It was a sleek black piece of hardware about the size of a refrigerator, as I recall. Much prettier than those 80s machines, although is it really a mainframe without at least one 9-track tape drive?)
Bear in mind mainframes aren’t about fast execution so much, they’re about massive parallelisation and I/O bandwidth.
http://www.cs.wisc.edu/multifacet/papers/ieeemicro08_virtual...
From the article:
“ So What Has IBM Done That is So Revolutionary? In the first paragraph, I mentioned that IBM Z is their big mainframe product – this is the big iron of the industry. It’s built better than your government-authorized nuclear bunker. These systems underpin the critical elements of society, such as infrastructure and banking. Downtime of these systems is measured in milliseconds per year, and they have fail safes and fail overs galore – with a financial transaction, when it is made, it has to be committed to all the right databases without fail, or even in the event of physical failure along the chain.
This is where IBM Z comes in. It’s incredibly niche, but has incredibly amazing design.”
1) How does a core know in which private cache of another core it can put the evicted data? Wouldn't that just remove data from that other core's cache that the other core needs?
2) Cores in today's processors can already read data from the private cache of another core (i.e., snooping), can they not?
Good question. There are many ways of handling this and I'm curious how IBM decided to implement this. Though it's unlikely they will divulge such internal implementation details.
> Wouldn't that just remove data from that other core's cache that the other core needs?
"This becomes important for cloud services (yes, IBM offers IBM Z in its cloud) where tenants do not need a full CPU, or for workloads that don’t scale exactly across cores."
> Cores in today's processors can already read data from the private cache of another core (i.e., snooping), can they not?
Depends on the exact CPU and its implementation. But yes, this idea of a "private cache" is pretty silly and misleading. Each cache is just a small subset of the system's memory. And all cores can issue memory reads which will eventually get the data from somewhere. Whether you're reading it from your own private cache, or some other core's private cache, a shared cache, or from DRAM, does not change the final result.
The only distinction here is in performance. Accessing a cache that is colocated to your core is much faster. Accessing a cache that is either shared or located elsewhere, is much slower. An approximate analogy would be using a us-east-1 ec2 instance to read from a us-east-1 RDS database, as opposed to a us-west-2 RDS database. The former database and its contents are certainly not "private", but they are a whole lot faster.
The CPUs have "read memory" and "write memory" as the only operations programs can see.
The cache policies operate asynchronously (because multiple cores simultaneously executing), to make those happen in the fastest way possible.
There's an endless variety of schemes and ways to design it, with the one huge requirement that it must ALWAYS be accurate.
But as long as you can satisfy that, you can do some goofy, crazy stuff. Might be faster, might be slower, but it will work.
There's the usual finance / banking guys. But also a lot of ERPs - the corporate bread and butter hr, Financials, crm, erm, scm, etc applications (I'm in this space, historically as sysadmin / light developer, then perf testing, infra architect, tech team lead, now as kind of a ops manager).
Over my 25 years and few dozen projects, mainframe was a significant portion of implementations and almost always at least on the table as potential platform.
Fwiw, What I always find fascinating though is that after many an implementation on "distributed platform", I. E. Unix Linux or Windows, as soon as any performance issue arises, there's a lot of calls to "move it back to mainframe" . I don't agree with that myself necessarily, but A lot of big enterprise shops feel that mainframe is an expensive pain, but reliable predictable well-performing expensive pain.
Is the mainframe really "more reliable" or "more performant" than a well provisioned cluster of commodity hw?
I mean after 20 years of optimising the SW stack, and monster xeons and tera-memory and fibre-channels and SSDs and everything so cheap and accessible. Is it really tech or just corporate inertia keeping this industry alive? ;)
It's worth noting that with modern computing systems, you could be deploying to a Z/OS system without even necessarily being aware of it.
The sheer amount of engineering that goes into these things is amazing.
Years ago, IBM had a partner offering mainframe Linux/Java "cloud servers". But that must not have added-up. They will tell their existing customers Z is great for these workloads but you don't see Google or Amazon buying them.
POWER9 has a slightly lower performance that amd64 (don't know about POWER10), but that is the main value proposition.
It would be interesting though to see what would happen if security researchers got the same cheap access to these platforms as to amd64.
Both IBM Z and POWER processors are vulnerable to a variety of spectre-style attacks.
They're definitely good. They're what the Blackbird and FSF-RYF-certified Talos use: https://www.raptorcs.com/content/base/products.html
And they have another architecture (s390x) for mainframes too.
"z13s introduce a new vector architecture and are the last z Systems servers to support running an operating system in ESA/390 architecture mode"
The removal of backwards compatibility meant you couldn't setup LPAR or VM with 31bit OS anymore
POWER is definitely used, but no idea of anywhere public.
Raptor unfortunately won't be doing a POWER10 box for a while if at all.
Not to mention Oracle, Db2, Epic.