The battery on my 13 year old ThinkPad T420 had just lasted an hour of a video call without trouble. The newer (by about 7 years) T470p only lasts about 15 minutes when doing very little 🙄
Took delivery of new work laptop today - Thinkpad P1 with a 16C/22T Intel Core i9 Ultra 185H, NVidia RTX2000-based GPU and a touch screen . And the modern wifi card is giving me 370/36Mbps on my home network which is as quick as the external connection so this will be a great boost over my aging T470p
I think we're going to get along well ;-)
Keeping the new laptop busy 🙂
#myCodesCompiling
It's not getting noticeably hot under this load so far (It's beein going for about ten minutes), which is nice. It's been running like this.
Core temps running at about +68°C
!!! EDIT: Ignore this post - I've concluded the tests were invalid !!!
Some tests on the new laptop with a small compile job:
On "CPUs" 0-11 (The Power ones, 6*2 threads) it builds in about 10.1 seconds when tied to a single "thread". On the "Efficient" ones it builds in about 15.5 seconds, and on the low power cores it's about 26.3 seconds.
I then tried with -j2 using two of the 22 threads:
- 1 thread on each of two P cores: 5.7s
- 2 threads on a single P core: 5.3s
Also, I've never really experimented with the "Power mode" options in Fedora/GNome, but for those tests which completed the builds in 10.1 seconds on one core, it's the same whether in "#Performance" or "Balanced" modes. If you switch the "Power Saver" it drops to 19.0 seconds.
I'll also note that it's great to have a system where I can play with CPU #affinity stuff in a controlled manner and also experiment with the three different cores in this machine!
Hmmm the other thing this new laptop should have is hardware #AV1 video encoding according to the CPU specs ... Something I posted about a year ago when some CPUs were starting to support it. Something else I can have a play with when I find a suitable #ffmpeg 😁
Shame I'm not going to be using this laptop for #immich 😉
(Someone will release a #RISCV SBC with that soon right?)
https://fosstodon.org/@sxa/113916723240097459
Another quick test since I was doing something that required me to rebuild openjdk from scratch ... Using "Power Saving" mode with all cores, jdk24 took 10m10s to compile
With full performance mode but only the E and LP cores in use it took
For comparison, full performance mode with all cores was 5m33
Power Saver was a lot quieter with the fan noise though!
The same build as above but just using the 6*2 "Power" cores:
- Performance mode: 7m50s
- Balanced mode: 8m45s
- Power Saving mode: 13m7s
@sxa So what your saying is you now need to decide how long you want the sword fight to last
@ben Absolutely ;-)
In reality I'm considering probably running it in power saving mode for now to keep the fan running slow most of the time, and possibly keep stuff like browser/slack explicitly tied to the efficient cores, corporate security stuff on the low power, and then save the big ones for compile jobs!
So I'm trying an experiment - partitioning my laptop's cores for certain tasks. I tried giving firefox two of the efficient cores but that was a bit too sluggish so I've upped it to 4 (all with a shared L3 cache) and it seems a lot happier. I've also tied Slack to two of those same four.
This way the high performance hyperthreaded cores can be dedicated kept for serious compile jobs etc. when needed. I think this will work out well. Does anyone else do this sort of thing?