4 ms·
1. Using uBlock Origin and NoScript would help 2. Sorry, but the AMD A4-1200 (2 Cores running at 1.0 (!) GHz, 4W TDP, Single Channel DDR3-1066[1]) was already
by Sweepi 2y ago
1. Using uBlock Origin and NoScript would help
2. Sorry, but the AMD A4-1200 (2 Cores running at 1.0 (!) GHz, 4W TDP, Single Channel DDR3-1066[1]) was already slow when it was new back in 2013, it was introduced by AMD as a low budget *Tablet* option
3. Regarding Video playback: As mention in the video, forcing Youtube to serve h264 should help, since the iGPU supports h264 decoding [2][3]
This also makes me wonder: What does Youtube serve on this old machines? On my old Vega 56 (UVD 7.0 h264/h265/JPEG decoding support), yt runs without issues, but on the displayed HD 8180 (UVD 4.2, h264 decoding support) it doesn't? My current system has a Nvidia 1050 and gets served AV1, which the 1050 also does not support in hardware.
My first instinct for yt's "auto" implementation would be to the serve a video in 480p and a codec the users hardware decoders supports, and if the user switches to a higher resolution, to serve it in av1 in order to preserve bandwidth. Maybe Youtube does not have access to the users hardware decoding capabilities, or they want to preserve bandwidth even at low resolutions.
[1] https://www.techpowerup.com/cpu-specs/a4-1200.c1706
[2] https://www.x.org/wiki/RadeonFeature/#index8h2
[3] https://en.wikipedia.org/wiki/Unified_Video_Decoder#Format_support
- miunau 2y agoI was using a netbook with a comparable CPU as a work machine around that time. Using the web with it wasn't fun back then either, on Windows or Linux. I don't think there's any point in time when these underpowered processors would've been fine to use for browsing mainstream sites.
- vel0city 2y agoWhile watching the video you can right click and choose "Stats for nerds". This opens an overlay in the top left corner showing a lot of detailed information about the video including video and audio codecs.