From: Frank Steinmetzger <Warp_7@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Would constant max CPU speed cause lockups?
Date: Sun, 6 Jun 2021 12:34:06 +0200 [thread overview]
Message-ID: <YLyknoDJzvG7PPF6@tp> (raw)
In-Reply-To: <YLux166+ZqKD72+b@waltdnes.org>
[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]
Am Sat, Jun 05, 2021 at 01:18:15PM -0400 schrieb Walter Dnes:
> A few years ago, I cheaped out and bought a low-powered Atom desktop
> with 8 gigs of RAM. Looking back, that was a mistake. It would default
> to 480p or at best 720p on Youtube. But I wrote a nifty bash script
> that manually put the CPU into "userspace" mode, and selected the
> maximum available CPU speed. I finally got Youtube with steady playback
> at 1080p... YAY!
OT, but an input to this aspect:
in-browser playback has always been a lackluster for me. It gobbles up CPU
cycles and makes the fans spin. Therefore by now it’s been engraved into my
muscle memory to copy the URL, download it and play it with
$FAVORITE_VIDEO_PLAYER.
I had a go at my Eeepc Atom netbook a few months back to see whether I could
use it as a little home server for Nextcloud and the likes. I noticed that
it drew 14 W from the socket at idle. And its performance was actually much
worse than my raspi’s (which suckles maybe 4 W). So I stowed it for good.
Pity, the haptic was not bad, but that’s the circle of life.
--
Grüße | Greetings | Qapla’
Please do not share anything from, with or about me on any social network.
If your laundry just wouldn’t become white,
may be that’s because it is coloured.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-06-06 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-05 17:18 [gentoo-user] Would constant max CPU speed cause lockups? Walter Dnes
2021-06-05 17:37 ` tastytea
2021-06-05 23:21 ` Michael
2021-06-06 0:42 ` Dottie Keogh
2021-06-06 10:34 ` Frank Steinmetzger [this message]
2021-06-06 18:04 ` Manuel McLure
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YLyknoDJzvG7PPF6@tp \
--to=warp_7@gmx.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox