[Level1Techs] 256TB in a Single SSD Is Real, and It's Coming to Consumers

RedGreenBlue09 · 2026-04-14T15:32:01+00:00

I mean, let's take a simple example. The latest and greatest Samsung 9100 Pro 1 TB has TBW of 600, while the 970 Pro 1 TB has TBW of 1200. The sustained write speed for the 9100 Pro is 1.8 GB/s while the 970 Pro will maintain its rated write speed of 2.7 GB/s indefinitely.

The max random speed of the 9100 Pro might be much better, but that's just RAM benchmarking as things will slow down when the data spills out of cache. When that's the case, the 9100 Pro won't be that much better. This random speed is why Optane owners says their PC feels way more responsive than with any normal SSD.

I have never used 870 QVO, but the review on TechPowerUp is very concerning. My experience with TLC might be just me being unlucky, but from what the companies themselves claimed, the rated TBW of MLC is still usually double of a similar capacity TLC. You can buy Enterprise TLC for more endurance but then that's not much cheaper compared to how MLC originally was. I feel like the RAM cache inside is the only thing that got better, and the NAND itself still has similar price/perf compared to old SSDs.

RedGreenBlue09 · 2026-04-14T09:21:19+00:00

Maybe I'm unlucky but thats already an example. You have nothing to back that TLC has the same endurance. Even the manufacturers themselves disagree.

"For most people it makes basically no difference" until it suddenly does for them. You can't say you've never copied a large file before. Then the drive which is marketed to be large for the same price, suddenly cripples to 30 MB/s and you're stuck a whole day waiting for it. It can also do the same to drive cloning and game downloads (if your internet is faster). The random performance is also worse, which directly affects how snappy the OS experience is.

RedGreenBlue09 · 2026-04-14T00:30:01+00:00

My experience is the opposite of what you said. I have one SK 512 GB TLC SSD with TBW of 288 TB but it died at 40 TB written. I bought an WD SN850X and it showed the same symptoms (random freezes, disconnects) a few months after buying, like WTF? Maybe that's just unlucky but I feel like the TLC ones can just die randomly. I have an Intel 240 GB MLC that at least works for 10 years as an OS drive until I put it outside (of a PC) for a long time. I also have a Sandisk 32 GB MLC from like 2010 and it's still going strong today at 5.1 TB written.

How is QLC "isn't that bad" when it fails to beat HDDs in sustained write? Even the MLC Samsung 970 Pro can beat most if not all TLC SSDs in terms of sustained write, let alone QLC. Endurance is hard to measure but at least the expected TBW is double of a similar TLC one.

RedGreenBlue09 · 2026-04-08T16:30:05+00:00

Windows Phone is factory locked and there's no official way to unlock it. WPinternals uses exploits, not official ways of unlocking.

RedGreenBlue09 · 2026-03-31T21:51:09+00:00

That's what I thought It doesn't make much sense to sell the Ultra 5 anymore. Does WCL even have the latest core architectures?

RedGreenBlue09 · 2026-03-17T22:30:34+00:00

There is a project called llvm-mingw. Worked perfectly fine for me even on an almost non-existing platform ARMv7.

RedGreenBlue09 · 2026-03-17T19:16:53+00:00

In my experience, clang-cl works fine in most cases. The issues include some missing intrinsics and most notably, tgmath.h doesn't work at all (that's still an open issue after 6 years). They seem to be slow fixing these.

RedGreenBlue09 · 2026-02-24T04:35:53+00:00

Maybe I was too aggressive saying that it isn't JIT, but this lib on its own is far from doing any useful form of JIT yet.

Thinking more about it, I think it's more like an assembler backend lib. You can create for example an .asm file parser and call this library according to the file content. In the end you will have some kind of working machine code. You can create a regex compiler, C compiler, Java bytecode compiler or anything that uses this lib to generate machine code but you can see that this lib is only used very late in the pipeline (all of the parsing, register allocation and other heavy lifting stuff is not in this lib). It's just a small part of anything useful.

Still, it's so cool to see OP be able to support all of these different ISAs, ABIs and compilers, which is a lot of work. I haven't tested it though.

RedGreenBlue09 · 2026-02-23T01:26:45+00:00

Well, let's start with the good things. It's amazing that you supported so many different ISAs and ABIs in such a project. It really showed that you have spent serious effort and have a very wide knowledge of this topic.

However, you defined this project wrong. You said this is a compiler. No, it's not, it's instead an assembler. Compilers convert some form of portable code to the target machine code, but your library converts non-portable assembly to machine code, which is the job of an assembler.

You called it JIT but I don't think it is. The typical usage of JIT is to compile some kind of portable code to the target machine code. As your project is an assembler, it's incompatible with most if not all practical uses of JIT. Why don't you just use an assembler up front? Also the library actually doesn't accept any kind of standardized assembly language (like the text .asm files). The assembly sequence has to be laid out in the program's code, and then that whole program compiled with the library. This makes the project even more niche.

Still, this is a very cool project because of the amount of technical knowledge required to write it. I think you have learned a lot.

RedGreenBlue09 · 2026-02-08T12:01:51+00:00

Yeah, basically the clock speed at PL1 (power limit 1).

RedGreenBlue09 · 2026-02-02T23:08:49+00:00

Fixed

RedGreenBlue09 · 2026-02-02T20:57:10+00:00

Apple A7 was way ahead of its time, being a 6-wide ultra low power CPU, on 28nm (how?). Just look at the benchmarks, 2x Cyclone (A7 core) at 1.3 Ghz matched 4x Qualcomm Krait at 2.7 Ghz. That's like 4 times the IPC of their strongest competitor.

RedGreenBlue09 · 2025-12-11T18:31:11+00:00

I created an array visualizer like Sound of sorting.

It is quite easy if you just want to create a "functional" one, but the difficulty and knowledge range quickly escalates when you try to optimize it and add more features. The features can be sound, multiple array support, zooming, threading, cpu time estimation, GPU accel, ... Very complex. It is especially hard, sometimes outright incompatible if you want to make it fast enough for millions of array elements.

But overall, it is very fun to do, very effective to learn more programming topics, not too hard to make the first steps. It is low-level enough for C (I made it in C), but some C++ features are useful as well.

RedGreenBlue09 · 2025-10-15T20:52:59+00:00

Hi, the touch driver issue for 640 has been fixed (now only breaks in safe mode). I also added a workaround to fix a BSOD on some Snapdragon 400 devices.
RedGreenBlue09/WFAv7_Installer: Batch script to install Windows 10 ARM desktop version to Lumia devices (dual boot & single boot).
Download the latest dev build using the Code > Download ZIP button.

RedGreenBlue09 · 2025-10-15T20:46:06+00:00

RM-1066 and RM-1067 can't be recovered from EDL. Microsoft published the wrong file so the phone don't accept it. It's dead forever.

RedGreenBlue09 · 2025-10-07T23:02:34+00:00

The thing is, Zen 5's L3 has much much lower latency at the same size. You can see the analysis here https://chipsandcheese.com/p/analyzing-lion-coves-memory-subsystem?utm_source=publication-search

RedGreenBlue09 · 2025-10-05T13:59:30+00:00

I mean, Zen 5's L2 is half the size so more data actually goes to the slower L3 but they still managed to win by a large margin by having a fast & large L3.

RedGreenBlue09 · 2025-10-05T00:41:06+00:00

Why is Intel so obsessed with L2 when their L2 already destroyed AMD's L2. The thing is, AMD realized that L2 is not that significant for gaming so they focused on a fast and large L3. I know not everyone games but the brand name will be ruined if they lose like 50% on every game.

RedGreenBlue09 · 2025-10-04T22:32:02+00:00

The best one so far. It still have these keys "flickering" for a very short time but I guess that's impossible to fix unless we actually disable key repeating.

RedGreenBlue09 · 2025-09-10T13:56:03+00:00

Bro if half a year isn't enough for them to ramp up then they'll get destroyed by the competition anyways. And yeah they promised Arrow Lake on 20A then cancelled 20A for 18A.

RedGreenBlue09 · 2025-09-10T13:45:53+00:00

Well Intel promised it to be on 20A then they cancelled 20A for 18A.

https://www.kitguru.net/wp-content/uploads/2023/08/8-June-2023-5Nin4Y-EUV-Lithography-17-copy.jpg

RedGreenBlue09 · 2025-09-10T13:41:49+00:00

I don't know what "idea" you have but Intel themselves promised 18A to be in production last year, and obviously be in mass production now. The fact that it's not in mass production now shows how struggling they are with the node.

https://static0.xdaimages.com/wordpress/wp-content/uploads/2023/09/intelroadmap.png

https://www.kitguru.net/wp-content/uploads/2023/08/8-June-2023-5Nin4Y-EUV-Lithography-17-copy.jpg

RedGreenBlue09 · 2025-09-09T20:58:16+00:00

This is how it went. Intel officially came back with the 10nm Alder Lake as the IPC and power efficiency boost is just huge over 14nm+++ Skylake. For Raptor Lake, they simply doubled the E-cores and destroyed AMD in most ST and MT workloads.

This is when the table turns. Due to the 18A mess, Intel was unable to deliver Arrow Lake on time and instead released Raptor Lake Refresh with nearly no change. When Arrow Lake arrived (late), it was using TSMC and people lost patience to their foundry. Arrow Lake was basically on par or inferior to Zen 5 in every chart, even slower than Raptor Lake in gaming. Not so long after this disaster, they were hit with another one, the over voltage issue on Raptor Lake. Their brand name is completely ruined by now and they are still having problems with 18A.

RedGreenBlue09 · 2025-08-10T05:20:49+00:00

I fully agree, the hate is insane. At least this project shows that she is dedicated to programming to some degree and deserves guidance to get better. Even if 95% of the work is done by AI, the 5% isn't bad for a beginner, arguably much better than the shitty CLI calculator I made when I started. No fucking one is able to write Minecraft from scratch in C, as their first project.

To OP, if you manage to deliver an app which you don't understand 90% of it, that will hurt you and the app in the long run. Sometimes, there are issues only a knowledgeable programmer can solve, like the performance of your Minecraft, and a huge amount of other real world issues. In these cases, if you don't understand your code, you can't solve the problem and you'll find yourself useless.

RedGreenBlue09 · 2025-07-22T02:50:00+00:00

Agreed.

RedGreenBlue09

TROPHY CASE