blob: b545837a78af36936cb2ce63cb584ee0e9dec34b (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
|
Slower Box64 startup time on AWS Graviton2 compared to Raspberry Pi 5
Hello, I'm new to box64 and currently experimenting with it. I noticed that Box64 startup time is slower on my setup (Graviton2) compared to a Raspberry Pi 5 demo.
In this [youtube video](https://youtu.be/f7a7sJF3lYo?si=qcrfVxMr-UC6oIoU&t=462), Box64 appears to launch a Factorio server in about 2 seconds on a Pi 5. That setup follows the [PiMyLifeUp guide](https://pimylifeup.com/raspberry-pi-x64/).
I'm measuring the time from whenI press enter to when the first factorio server log show up.
I did the same setup steps on an AWS EC2 instance (Graviton2 / Neoverse N1, Ubuntu 22.04, 6.8.0-1029-aws), but the startup takes about 7 seconds instead.
I built box64 with
`cmake .. -DARM64=1 -DCMAKE_BUILD_TYPE=RelWithDebInfo`
Here’s my CPU info:
```
root@ip-172-31-33-12:~# lscpu
Architecture: aarch64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Vendor ID: ARM
BIOS Vendor ID: AWS
Model name: Neoverse-N1
BIOS Model name: AWS Graviton2 AWS Graviton2 CPU @ 2.5GHz
BIOS CPU family: 257
Model: 1
Thread(s) per core: 1
Core(s) per socket: 8
Socket(s): 1
Stepping: r3p1
BogoMIPS: 243.75
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
Caches (sum of all):
L1d: 512 KiB (8 instances)
L1i: 512 KiB (8 instances)
L2: 8 MiB (8 instances)
L3: 32 MiB (1 instance)
NUMA:
NUMA node(s): 1
NUMA node0 CPU(s): 0-7
Vulnerabilities:
Gather data sampling: Not affected
Itlb multihit: Not affected
L1tf: Not affected
Mds: Not affected
Meltdown: Not affected
Mmio stale data: Not affected
Reg file data sampling: Not affected
Retbleed: Not affected
Spec rstack overflow: Not affected
Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Spectre v1: Mitigation; __user pointer sanitization
Spectre v2: Mitigation; CSV2, BHB
Srbds: Not affected
Tsx async abort: Not affected
```
Both Pi 5 and Graviton2 are based on Cortex-A76, so I expected similar performance.
Is there anything I can try to reduce startup time?
Thanks!
|