MiniPC X1 de Youyeetoo: potencia y rendimiento en la palma de tu mano - Página 11 de 12

Contenido

Ubuntu 23.04

Como hacemos habitualmente hemos instalado Ubuntu en una segunda partición del SSD y hemos hecho las pruebas típicas.

pharizna@pharizna-X1:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=23.04
DISTRIB_CODENAME=lunar
DISTRIB_DESCRIPTION="Ubuntu 23.04"
pharizna@pharizna-X1:~$ uname -a
Linux pharizna-X1 6.2.0-39-generic #40-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:18:00 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
pharizna@pharizna-X1:~$ free -mh
               total       usado       libre  compartido   búf/caché   disponible
Mem:            15Gi       1,9Gi        12Gi       471Mi       1,8Gi        13Gi
Inter:         4,0Gi          0B       4,0Gi
pharizna@pharizna-X1:~$ df -mh
S.ficheros     Tamaño Usados  Disp Uso% Montado en
tmpfs            1,6G   2,0M  1,6G   1% /run
/dev/nvme0n1p5   101G    12G   84G  13% /
tmpfs            7,8G      0  7,8G   0% /dev/shm
tmpfs            5,0M   8,0K  5,0M   1% /run/lock
/dev/nvme0n1p1    96M    33M   64M  34% /boot/efi
tmpfs            1,6G   108K  1,6G   1% /run/user/1000

pharizna@pharizna-X1:~$ cat /etc/lsb-release

DISTRIB_ID=Ubuntu

DISTRIB_RELEASE=23.04

DISTRIB_CODENAME=lunar

DISTRIB_DESCRIPTION="Ubuntu 23.04"

pharizna@pharizna-X1:~$ uname -a

Linux pharizna-X1 6.2.0-39-generic #40-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:18:00 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

pharizna@pharizna-X1:~$ free -mh

total usado libre compartido búf/caché disponible

Mem: 15Gi 1,9Gi 12Gi 471Mi 1,8Gi 13Gi

Inter: 4,0Gi 0B 4,0Gi

pharizna@pharizna-X1:~$ df -mh

S.ficheros Tamaño Usados Disp Uso% Montado en

tmpfs 1,6G 2,0M 1,6G 1% /run

/dev/nvme0n1p5 101G 12G 84G 13% /

tmpfs 7,8G 0 7,8G 0% /dev/shm

tmpfs 5,0M 8,0K 5,0M 1% /run/lock

/dev/nvme0n1p1 96M 33M 64M 34% /boot/efi

tmpfs 1,6G 108K 1,6G 1% /run/user/1000

También, como no podía ser menos, hemos utilizado el típico SBC-BENCH (versión Review, claro)

pharizna@pharizna-X1:~$ wget https://raw.githubusercontent.com/ThomasKaiser/sbc-bench/master/sbc-bench.sh
--2024-05-15 23:53:28--  https://raw.githubusercontent.com/ThomasKaiser/sbc-bench/master/sbc-bench.sh
Resolviendo raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.110.133, 185.199.108.133, 185.199.111.133, ...
Conectando con raw.githubusercontent.com (raw.githubusercontent.com)[185.199.110.133]:443... conectado.
Petición HTTP enviada, esperando respuesta... 200 OK
Longitud: 434891 (425K) [text/plain]
Guardando como: ‘sbc-bench.sh’

sbc-bench.sh                 100%[===========================================>] 424,70K  --.-KB/s    en 0,02s  

2024-05-15 23:53:28 (20,5 MB/s) - ‘sbc-bench.sh’ guardado [434891/434891]

pharizna@pharizna-X1:~$ sudo /bin/bash ./sbc-bench.sh -r
[sudo] contraseña para pharizna:
Starting to examine hardware/software for review purposes...

Average load and/or CPU utilization too high (too much background activity). Waiting...

Too busy for benchmarking: 23:53:58 up 6 min,  3 users,  load average: 2.10, 1.27, 0.56,  cpu: 21%
Too busy for benchmarking: 23:54:03 up 6 min,  3 users,  load average: 1.93, 1.25, 0.56,  cpu: 1%
Too busy for benchmarking: 23:54:08 up 6 min,  3 users,  load average: 1.78, 1.23, 0.56,  cpu: 1%
Too busy for benchmarking: 23:54:13 up 6 min,  3 users,  load average: 1.64, 1.21, 0.55,  cpu: 1%
Too busy for benchmarking: 23:54:18 up 6 min,  3 users,  load average: 1.50, 1.19, 0.55,  cpu: 1%
Too busy for benchmarking: 23:54:23 up 6 min,  3 users,  load average: 1.38, 1.17, 0.55,  cpu: 1%
Too busy for benchmarking: 23:54:28 up 6 min,  3 users,  load average: 1.35, 1.17, 0.55,  cpu: 1%

sbc-bench v0.9.65

Installing needed tools: apt-get -f -qq -y install gcc make build-essential lm-sensors powercap-utils curl git sysstat links mmc-utils smartmontools stress-ng p7zip, tinymembench, ramlat, mhz, cpufetch, cpuminer. Done.
Checking cpufreq OPP. Done.
Executing tinymembench. Done.
Executing RAM latency tester. Done.
Executing OpenSSL benchmark. Done.
Executing 7-zip benchmark. Done.
Throttling test: heating up the device, 5 more minutes to wait. Done.
Checking cpufreq OPP again. Done (11 minutes elapsed).

Results validation:

  * Measured clockspeed not lower than advertised max CPU clockspeed
  * No swapping
  * Background activity (%system) OK
  * Too much other background activity: 4% avg, 21% max -> https://tinyurl.com/mr2wy5uv
  * Powercap detected. Details: "sudo powercap-info -p intel-rapl" -> https://tinyurl.com/4jh9nevj

Full results uploaded to https://sprunge.us/rvOq9q

# youyeetoo X1 SBC  / Celeron N5105 @ 2.00GHz

Tested with sbc-bench v0.9.65 on Thu, 16 May 2024 00:07:36 +0200. Full info: [https://sprunge.us/rvOq9q](http://sprunge.us/rvOq9q)

### General information:

    Information courtesy of cpufetch:
   
    Name:                Intel Celeron N5105
    Microarchitecture:   Tremont
    Technology:          10nm
    Max Frequency:       2.900 GHz
    Cores:               4 cores
    AVX:                 No
    FMA:                 No
    L1i Size:            32KB (128KB Total)
    L1d Size:            32KB (128KB Total)
    L2 Size:             1.5MB
    L3 Size:             4MB
   
    Celeron N5105 @ 2.00GHz, Kernel: x86_64, Userland: amd64
   
    CPU sysfs topology (clusters, cpufreq members, clockspeeds)
                     cpufreq   min    max
     CPU    cluster  policy   speed  speed   core type
      0        0        0      800    2900       -
      1        0        1      800    2900       -
      2        0        2      800    2900       -
      3        0        3      800    2900       -

15827 KB available RAM

### Policies (performance vs. idle consumption):

Status of performance related policies found below /sys:

    /sys/module/pcie_aspm/parameters/policy: [default] performance powersave powersupersave

### Clockspeeds (idle vs. heated up):

Before at 72.0°C:

    cpu0: OPP: 2900, Measured: 2828      (-2.5%)

After at 102.0°C:

    cpu0: OPP: 2900, Measured: 2872

### Performance baseline

  * memcpy: 8105.7 MB/s, memchr: 11064.0 MB/s, memset: 8444.6 MB/s
  * 16M latency: 142.0 134.2 133.4 131.8 134.4 136.0 130.1 131.7
  * 128M latency: 154.2 157.6 162.1 165.5 154.8 155.7 156.9 161.7
  * 7-zip MIPS (3 consecutive runs): 10114, 10163, 10406 (10230 avg), single-threaded: 2877
  * `aes-256-cbc     461004.43k   749395.22k   790119.25k   800432.13k   803353.94k   800385.71k`
  * `aes-256-cbc     456592.10k   739133.38k   775887.62k   790321.15k   790197.59k   789954.56k`

### PCIe and storage devices:

  * Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet: Speed 2.5GT/s, Width x1, driver in use: r8169,
  * 238.5GB "Lexar SSD NM620 256GB" SSD as /dev/nvme0: Speed 8GT/s, Width x4, 0% worn out, drive temp: 58°C, ASPM Disabled
  * 16MB SPI NOR flash, drivers in use: spi-nor/intel-spi

### Challenging filesystems:

The following partitions are NTFS: nvme0n1p3,nvme0n1p4 -> https://tinyurl.com/mv7wvzct

### Swap configuration:

  * /swap.img on /dev/nvme0n1p5: 4.0G (0K used)

### Software versions:

  * Ubuntu 23.04 (lunar)
  * Compiler: /usr/bin/gcc (Ubuntu 12.3.0-1ubuntu1~23.04) 12.3.0 / x86_64-linux-gnu
  * OpenSSL 3.0.8, built on 7 Feb 2023 (Library: OpenSSL 3.0.8 7 Feb 2023)    

### Kernel info:

  * `/proc/cmdline: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=a170f22b-c908-4621-b04e-5a6ec80d6b28 ro quiet splash vt.handoff=7`
  * Vulnerability Mmio stale data:      Mitigation; Clear CPU buffers; SMT disabled
  * Vulnerability Spec store bypass:    Mitigation; Speculative Store Bypass disabled via prctl
  * Vulnerability Spectre v1:           Mitigation; usercopy/swapgs barriers and __user pointer sanitization
  * Vulnerability Srbds:                Vulnerable: No microcode
  * Kernel 6.2.0-39-generic / CONFIG_HZ=250

Waiting for the device to cool down....................................................................... 62.0°C

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

pharizna@pharizna-X1:~$ wget https://raw.githubusercontent.com/ThomasKaiser/sbc-bench/master/sbc-bench.sh

--2024-05-15 23:53:28-- https://raw.githubusercontent.com/ThomasKaiser/sbc-bench/master/sbc-bench.sh

Resolviendo raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.110.133, 185.199.108.133, 185.199.111.133, ...

Conectando con raw.githubusercontent.com (raw.githubusercontent.com)[185.199.110.133]:443... conectado.

Petición HTTP enviada, esperando respuesta... 200 OK

Longitud: 434891 (425K) [text/plain]

Guardando como: ‘sbc-bench.sh’

sbc-bench.sh 100%[===========================================>] 424,70K --.-KB/s en 0,02s

2024-05-15 23:53:28 (20,5 MB/s) - ‘sbc-bench.sh’ guardado [434891/434891]

pharizna@pharizna-X1:~$ sudo /bin/bash ./sbc-bench.sh -r

[sudo] contraseña para pharizna:

Starting to examine hardware/software for review purposes...

Average load and/or CPU utilization too high (too much background activity). Waiting...

Too busy for benchmarking: 23:53:58 up 6 min, 3 users, load average: 2.10, 1.27, 0.56, cpu: 21%

Too busy for benchmarking: 23:54:03 up 6 min, 3 users, load average: 1.93, 1.25, 0.56, cpu: 1%

Too busy for benchmarking: 23:54:08 up 6 min, 3 users, load average: 1.78, 1.23, 0.56, cpu: 1%

Too busy for benchmarking: 23:54:13 up 6 min, 3 users, load average: 1.64, 1.21, 0.55, cpu: 1%

Too busy for benchmarking: 23:54:18 up 6 min, 3 users, load average: 1.50, 1.19, 0.55, cpu: 1%

Too busy for benchmarking: 23:54:23 up 6 min, 3 users, load average: 1.38, 1.17, 0.55, cpu: 1%

Too busy for benchmarking: 23:54:28 up 6 min, 3 users, load average: 1.35, 1.17, 0.55, cpu: 1%

sbc-bench v0.9.65

Installing needed tools: apt-get -f -qq -y install gcc make build-essential lm-sensors powercap-utils curl git sysstat links mmc-utils smartmontools stress-ng p7zip, tinymembench, ramlat, mhz, cpufetch, cpuminer. Done.

Checking cpufreq OPP. Done.

Executing tinymembench. Done.

Executing RAM latency tester. Done.

Executing OpenSSL benchmark. Done.

Executing 7-zip benchmark. Done.

Throttling test: heating up the device, 5 more minutes to wait. Done.

Checking cpufreq OPP again. Done (11 minutes elapsed).

Results validation:

* Measured clockspeed not lower than advertised max CPU clockspeed

* No swapping

* Background activity (%system) OK

* Too much other background activity: 4% avg, 21% max -> https://tinyurl.com/mr2wy5uv

* Powercap detected. Details: "sudo powercap-info -p intel-rapl" -> https://tinyurl.com/4jh9nevj

Full results uploaded to https://sprunge.us/rvOq9q

# youyeetoo X1 SBC / Celeron N5105 @ 2.00GHz

Tested with sbc-bench v0.9.65 on Thu, 16 May 2024 00:07:36 +0200. Full info: [https://sprunge.us/rvOq9q](http://sprunge.us/rvOq9q)

### General information:

Information courtesy of cpufetch:

Name: Intel Celeron N5105

Microarchitecture: Tremont

Technology: 10nm

Max Frequency: 2.900 GHz

Cores: 4 cores

AVX: No

FMA: No

L1i Size: 32KB (128KB Total)

L1d Size: 32KB (128KB Total)

L2 Size: 1.5MB

L3 Size: 4MB

Celeron N5105 @ 2.00GHz, Kernel: x86_64, Userland: amd64

CPU sysfs topology (clusters, cpufreq members, clockspeeds)

cpufreq min max

CPU cluster policy speed speed core type

0 0 0 800 2900 -

1 0 1 800 2900 -

2 0 2 800 2900 -

3 0 3 800 2900 -

15827 KB available RAM

### Policies (performance vs. idle consumption):

Status of performance related policies found below /sys:

/sys/module/pcie_aspm/parameters/policy: [default] performance powersave powersupersave

### Clockspeeds (idle vs. heated up):

Before at 72.0°C:

cpu0: OPP: 2900, Measured: 2828 (-2.5%)

After at 102.0°C:

cpu0: OPP: 2900, Measured: 2872

### Performance baseline

* memcpy: 8105.7 MB/s, memchr: 11064.0 MB/s, memset: 8444.6 MB/s

* 16M latency: 142.0 134.2 133.4 131.8 134.4 136.0 130.1 131.7

* 128M latency: 154.2 157.6 162.1 165.5 154.8 155.7 156.9 161.7

* 7-zip MIPS (3 consecutive runs): 10114, 10163, 10406 (10230 avg), single-threaded: 2877

* `aes-256-cbc 461004.43k 749395.22k 790119.25k 800432.13k 803353.94k 800385.71k`

* `aes-256-cbc 456592.10k 739133.38k 775887.62k 790321.15k 790197.59k 789954.56k`

### PCIe and storage devices:

* Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet: Speed 2.5GT/s, Width x1, driver in use: r8169,

* 238.5GB "Lexar SSD NM620 256GB" SSD as /dev/nvme0: Speed 8GT/s, Width x4, 0% worn out, drive temp: 58°C, ASPM Disabled

* 16MB SPI NOR flash, drivers in use: spi-nor/intel-spi

### Challenging filesystems:

The following partitions are NTFS: nvme0n1p3,nvme0n1p4 -> https://tinyurl.com/mv7wvzct

### Swap configuration:

* /swap.img on /dev/nvme0n1p5: 4.0G (0K used)

### Software versions:

* Ubuntu 23.04 (lunar)

* Compiler: /usr/bin/gcc (Ubuntu 12.3.0-1ubuntu1~23.04) 12.3.0 / x86_64-linux-gnu

* OpenSSL 3.0.8, built on 7 Feb 2023 (Library: OpenSSL 3.0.8 7 Feb 2023)

### Kernel info:

* `/proc/cmdline: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=a170f22b-c908-4621-b04e-5a6ec80d6b28 ro quiet splash vt.handoff=7`

* Vulnerability Mmio stale data: Mitigation; Clear CPU buffers; SMT disabled

* Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl

* Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization

* Vulnerability Srbds: Vulnerable: No microcode

* Kernel 6.2.0-39-generic / CONFIG_HZ=250

Waiting for the device to cool down....................................................................... 62.0°C

Comparando los resultados con los obtenidos en la misma prueba con el R86S o el R1 Pro, en aquella ocasión la CPU se «sobrecalentó» hasta los 63-68ºC y en el X2L llegó a los 94º… en este caso y como esperábamos al optimizar la BIOS para reducir el ruido la temperatura ha subido hsta los 102ºC 🙁 . Lo mejor de todo es que, tal y como comentábamos con anterioridad el ruido del ventilador es prácticamente inaudible y tan solo se escucha ligeramente cuando va al máximo de velocidad. En cualquier caso el ruido es mucho menor que en el caso del RS86S T4, el R1Pro de iKoolCore o el Nimbustor 2, NAS de Asustor…. que tiene el mismo procesador pero no alcanza temperaturas tan elevadas.

6897

3 Comments

Inline Feedbacks

Ver todos los comentarios

Admin

Pharizna

5 meses antes

Como siempre se nos quedan cosas en el tintero pero no podemos seguir reteniendo la salida de nuestras revisiones … aunque en este caso el retraso de esta semana se ha debido a mi «rotura de cráneo» del pasado domingo

Bueno a lo que vamos y pienso que puede servir de ayuda. ¿Os habéis preguntado en qué puede influir sobre un PC funcionando el cambio de su BIOS?

Tres posibilidades:
a) No influye
b) El PC no arranca
c) Si es con Windows… da algunos «problemillas» fácilmente subsanables.

En este caso la respuesta es la C … en la que yo nunca habría pensado ¿y vosotros?

Pues sí, parece que M$ utiliza datos del hard/BIOS para la seguridad de acceso a Windows por lo que el PIN deja de funcionar tocando la BIOS. Afortunadamente la solución es sencilla ya que basta con definir un nuevo PIN y listo

Aunque evidentemente el valor del TDP nos da una idea del consumo energético de un ordenador el valor real suele ser mayor, del orden de 2 veces.

Por ejemplo con este X1 funcionando en Windows el consumo medio suele ser de unos 15 W y el máximo de unos 25.

Desgraciadamente, por ahora, tendremos que esperar un poco más para recibir el BY52 o mejor aún un nuevo modelo con procesador mejor que el Intel N100 que parece ser el utilizado de forma mayoritaria por el resto de fabricantes