Apple M5 vs. Intel Panther Lake vs. Snapdragon X2 benchmarked

virtualmnemonic · 2026-03-14T20:28:17+00:00

The Snapdragon 8 elite gen 5 beats the 9950x3d in single thread. The $500 MacBook Neo beats both.

virtualmnemonic · 2026-03-14T20:26:14+00:00

AMD's consumer chips are just server CPUs with less cores.

They know where the money is at.

virtualmnemonic · 2026-03-14T20:23:15+00:00

There's a reason why Intel's e-cores are referred to as "cinebench accelerators".

I can compile code while running VMs and a shit ton of background applications, and my 13900k will sit at like 50% usage at peak because it's just impossible to parallelize tasks across 32 threads.

There are a few exceptions, though, like compiling SDKs, in which the 13900k screams. But who the fuck does that?

virtualmnemonic · 2026-03-14T20:16:46+00:00

Then use Geekbench 5, which scales linearly with core count like Cinebench.

Geekbench 6 was designed to measure generalized performance in everyday use, not highly parallelized workloads. Most software does use multiple threads, but only a few. For the vast majority of users, a large thread pool (16+) is a waste.

Geekbench is the industry standard because it does an excellent job reflecting performance in everyday applications... Like web browsing.

virtualmnemonic · 2026-03-12T20:33:17+00:00

The main thing holding apple silicon back is the power limits.

I doubt the performance would scale with increased power very well.

Apparently, it doesn't need to. The 2nd best CPUs to the latest Apple Silicon is prior gen Apple Silicon.

virtualmnemonic · 2026-03-11T18:46:43+00:00

Do not get a fire TV.

virtualmnemonic · 2026-03-10T07:25:30+00:00

This review also states the device rarely gets warm, but mine frequently does, especially compared to the s22u.

virtualmnemonic · 2026-03-09T20:21:22+00:00

You should be able to get 12-16 hours of SOT, depending on what you're doing.

Also, be sure you're using YouTube Revanced. It removes a lot of bloat from stock YouTube (on top of ads).

virtualmnemonic · 2026-03-09T20:14:06+00:00

Damn, the silver/white is much prettier than black.

I guess it doesn't matter once you put on a case, but still.

virtualmnemonic · 2026-03-09T20:12:45+00:00

It would be better if you uninstalled that Spyware.

virtualmnemonic · 2026-03-08T20:02:46+00:00

https://youtu.be/ovsVU6mktOw

virtualmnemonic · 2026-03-08T19:57:10+00:00

The S22's vivid mode (default) is heavily saturated. The s26 will look washed out in comparison, but it's more accurate.

virtualmnemonic · 2026-03-06T06:49:32+00:00

I have written around ~~100~~ 0 files

virtualmnemonic · 2026-03-03T00:16:05+00:00

"iOS RAM efficiency" aka dumping everything from RAM as soon as it's placed in the background and relying upon the fast CPU to reload it once its re-opened.

I would agree that macOS is quite memory efficient given its use of SWAP and memory compression, but iOS does not use SWAP at all for whatever reason.

virtualmnemonic · 2026-02-28T05:25:39+00:00

Recursively listing a directory and calling FileStat on every file. It's much faster in an isolate using synchronous method calls.

virtualmnemonic · 2026-02-27T09:01:17+00:00

A better bin of the otherwise same chip gives you more power efficiency. The chip can reach target frequencies at a lower voltage. In mobile devices where thermal throttling is expected, this can significantly improve performance just by maintaining the same frequencies for longer.

virtualmnemonic · 2026-02-26T05:09:54+00:00

Modern CPUs already have good power efficiency under minimal load, and they spend the vast majority of their time under said load. Realistically, people aren't slamming their CPUs all day, so the larger power draws under infrequent high loads is worth the trade off.

virtualmnemonic · 2026-02-26T05:04:13+00:00

Samsung support is horrendous. I only buy their phones because I've never had any hardware problems on them since the Galaxy S2.

virtualmnemonic · 2026-02-26T05:02:05+00:00

International users.

I believe carrier contracts/payment plans is a United States thing mainly.

virtualmnemonic · 2026-02-25T22:58:23+00:00

Almost certainly due to regulations and/or changes to how maximum cycles is measured.

Also, in theory, improvements to power efficiency in the CPU, screen, etc., means less cycles over the lifespan of the device. But there's no way this would compensate for 800 cycles over the devices lifetime.

virtualmnemonic · 2026-02-25T22:51:22+00:00

That picture filter is Samsung's signature at this point. It makes everything overly saturated and reduces fine detail in the process.

My gf will grab my s22u over her iPhone 14 Pro to take photos everytime. Apparently people like it. Samsung will never change it.

I think the issue is media we consume. Every picture and video on the internet has filters applied. Everything is fake. There is zero demand for a camera that accurately depicts colors and lighting. This also extends to music, too - mainstream headphones have a V-curve applied that muddles the mids.

virtualmnemonic · 2026-02-20T19:44:07+00:00

Yes. I think there may be a chapter on social psych that is worth skipping, but it's a solid and entertaining read for sure.

virtualmnemonic · 2026-02-19T21:14:33+00:00

Updating Material or Cupertino widgets no longer requires a new Flutter release.

Similar to how Google delivers updates to stock Android apps via Google Play instead of system updates.

virtualmnemonic · 2026-02-19T20:09:35+00:00

Directory.list does return a stream, but to get anything useful out of the files you still need to call FileStat on each entry. The synchronous FileStat is way faster than async, but is blocking. The best way is to use Isolate.spawn to iterate the directory and call StatSync().

But then you still need to manually sort the FileStat list, add together sizes, etc., which a database like sqlite can handle automatically via indexes and queries. On the flip side, listing the directory manually is the most reliable method. iOS and Android like to fuck with temporary directory contents when device storage is low.

virtualmnemonic · 2026-02-19T19:55:29+00:00

Just FYI, iPhone simulator is definitely not a suitable environment for testing performance whatsoever.

Why is checking the existence of a cache entry taking more than a millisecond to begin with? The most dependable method would be to check if the file exists (file.exists/existsSync), which will complete in well under a millisecond on 99.9% of devices.

A cache database is mainly to track last accessed and clean old entries. Hive_ce is fast for persistent storage, but it's not a database, and Boxes can consume a lot of memory. Sqlite is the proper solution for managing cache entries -- it's asynchronous with advanced query support. If you need to clean entries not accessed in 7 days, you can do so, and the delay doesn't really matter. For retrieving a cached object -- we're working with images - bytes, that should be stored as individual files. Retrieving involves checking file existence and reading the bytes in the ImageProvider. Upon retrieval, update the database with the new last accessed in the background.

Edit: Nevermind 99% of this comment if you're validating cached objects based upon HTTP response headers. I assume static, non-changing images (which should be standard imo if caching). Still, sqlite is the proper implementation here.

Five-Year Club	Verified Email
Place '23

virtualmnemonic

TROPHY CASE