Re:Apple’s M1 Positioning Mocks the Entire x86 Business Model
by msie on Friday April 23, 2021 @02:04PM
(#26917420)
This guy seems to have pinpointed the problem: https://www.youtube.com/watch?v=FyMCoQmsv-I
The problem is unoptimized apps running on Rosetta2.
Re:Apple’s M1 Positioning Mocks the Entire x86 Business Model
by sillysaurusx on Friday April 23, 2021 @03:20PM
(#26918175)
Thank you for finding this!
Unfortunately, and somewhat sadly, and melanchololy, I must report that I've been at OS version 11.2.3 (the latest) and run almost zero Rosetta apps: KeepassX, Beyond Compare, and Optimal Layout; of those, Optimal Layout has read 100GB, which is almost nothing.
In comparison, my kernel_task process is at 43TB bytes written, and WindowServer is at 8TB read.
So, as with cancer, there are multiple contributing factors, and hopefully Apple will ship an update to fix it... someday.
Re:Apple’s M1 Positioning Mocks the Entire x86 Business Model
by ngcc_hk on Saturday April 24, 2021 @07:23AM
(#26924086)
Surprise. I bought the rose... theory. Sigh.
Re:Apple’s M1 Positioning Mocks the Entire x86 Business Model
by rjzzleep on Friday April 23, 2021 @01:03PM
(#26916776)
Well on Linux my 16GB thinkpad would thrash for more than 60 seconds unless I sysrq.
Re:Apple’s M1 Positioning Mocks the Entire x86 Business Model
by neycoda on Saturday April 24, 2021 @11:41AM
(#26925694)
Thrash is an odd word for an SSD... I mean, there's no moving parts, so I can't imagine how it's thrashing about.
Re:Apple’s M1 Positioning Mocks the Entire x86 Business Model
by bayindirh on Saturday April 24, 2021 @11:47AM
(#26925765)
Swamping an SSD with write requests and forcing it to write-level aggressively is trashing an SSD IMHO. Since it both silently grinds to fulfill the requests and loses a lot of lifespan during the process.
> I’m not exactly representative, but I think the stddev of usage patterns is high across developers.
When I'm in development mode with all cylinders firing, I have a single Eclipse window in CDT perspective, a couple of terminal tabs, Zeal (or Dash) for documentation and a couple of firefox tabs for documentation not available in Zeal.
Music is either supplied by a single YouTube tab or Spotify, and that's it.
The most unfortunate component is CPU in my case. I try to ooze every single bit of performance from it while running the application. Memory controller comes the second due to transfer operations but, I neither max out the RAM or cause system to do heavy swapping.
I'm always kind of conscious about the hardware resources of the system and minimize my resource usage habitually, without killing productivity.