I get to this task and it never finishes.
VPS 2GB RAM, 20GB Disk. Almalinux 8. Fresh install.
TASK [php/build-from-source : Compile PHP 8.1.21 (10+ minute wait)]
Is there a way to speed this up or use a binary initially and compile later?
I get to this task and it never finishes.
VPS 2GB RAM, 20GB Disk. Almalinux 8. Fresh install.
TASK [php/build-from-source : Compile PHP 8.1.21 (10+ minute wait)]
Is there a way to speed this up or use a binary initially and compile later?
There are 2 separate PHP builds, one for the websites and one for the panel. Ideally you’d want to build from source since it’s a 10% performance improvement. On a 500 ms pageload, that translates to a 50 ms improvement. At 2 requests/second, that’s a savings of 8,640 seconds each day or 72 hours per month; it’s an acceptable tradeoff.
CPU can be subdivided nearly an unlimited amount. You’ll fight for CPU scheduling on oversold hypervisors. It should take ~15 minutes at most to build. Here’s benchmark data from various VPS providers. On a 2 GB Linode, entire install takes ~45 minutes whereas Hetzner takes twice that with both “EPYC” processors.
Let it build. It’ll go onto the next step once completed.
On the 2 VPSs I have installed apiscp on this build step has taken multiple hours.
I think it may stall on the slowest VPS because I have gone to sleep on more than one ocasion and had to run the follow up install script.
So I asked can I install with just a binary and then compile later.
If it’s taking 6+ hours, you likely hit an OOM failure during build and it’s looping. Does this report anything?
grep -m1 failed=1 -B20 /root/apnscp-bootstrapper.log
If not, then I’d run yabs to evaluate VM performance. Builds on Vultr for me complete within 2 hours, which includes reporting every task to a database, so there is tremendous overhead. Without reporting, these builds complete within a hour.
grep -m1 failed=1 -B20 /root/apnscp-bootstrapper.log
No result from above.
If I run YABS what minimum result should I expect to be able to build it in 2 hours or less?
And again the binary first compile later method could be a thing.
It’s still running, you have a painfully slow CPU.
Here’s from a $10 2 GB Vultr instance, specifically this test build
Tue Mar 26 19:39:09 UTC 2024
Basic System Information:
---------------------------------
Uptime : 3 days, 26 hours, 0 minutes
Processor : Intel Core Processor (Broadwell, no TSX, IBRS)
CPU cores : 1 @ 2394.454 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ❌ Disabled
RAM : 1.9 GiB
Swap : 5.3 GiB
Disk : 51.5 GiB
Distro : AlmaLinux 8.9 (Midnight Oncilla)
Kernel : 4.18.0-513.18.1.el8_9.x86_64
VM Type : MICROSOFT
IPv4/IPv6 : ✔ Online / ✔ Online
IPv6 Network Information:
---------------------------------
ISP : The Constant Company
ASN : AS20473 The Constant Company, LLC
Host : Vultr Holdings, LLC
Location : Atlanta, Georgia (GA)
Country : United States
fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/vda2):
---------------------------------
Block Size | 4k (IOPS) | 64k (IOPS)
------ | --- ---- | ---- ----
Read | 149.48 MB/s (37.3k) | 224.98 MB/s (3.5k)
Write | 149.87 MB/s (37.4k) | 226.16 MB/s (3.5k)
Total | 299.35 MB/s (74.8k) | 451.14 MB/s (7.0k)
| |
Block Size | 512k (IOPS) | 1m (IOPS)
------ | --- ---- | ---- ----
Read | 226.05 MB/s (441) | 242.80 MB/s (237)
Write | 238.06 MB/s (464) | 258.97 MB/s (252)
Total | 464.12 MB/s (905) | 501.77 MB/s (489)
Geekbench 5 Benchmark Test:
---------------------------------
Test | Value
|
Single Core | 561
Multi Core | 561
Full Test | https://browser.geekbench.com/v5/cpu/22351764
And another from a $5 1 GB Linode instance running code.apisnetworks.com,
Tue Mar 26 19:39:09 UTC 2024
Basic System Information:
---------------------------------
Uptime : 70 days, 19 hours, 6 minutes
Processor : AMD EPYC 7713 64-Core Processor
CPU cores : 1 @ 2000.000 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ❌ Disabled
RAM : 950.7 MiB
Swap : 4.5 GiB
Disk : 24.0 GiB
Distro : Rocky Linux 8.9 (Green Obsidian)
Kernel : 4.18.0-513.11.1.el8_9.x86_64
VM Type : KVM
IPv4/IPv6 : ✔ Online / ✔ Online
IPv6 Network Information:
---------------------------------
ISP : Akamai Technologies, Inc.
ASN : AS63949 Akamai Connected Cloud
Host : Linode
Location : Ashburn, Virginia (VA)
Country : United States
fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/sda):
---------------------------------
Block Size | 4k (IOPS) | 64k (IOPS)
------ | --- ---- | ---- ----
Read | 165.95 MB/s (41.4k) | 2.17 GB/s (33.9k)
Write | 166.39 MB/s (41.5k) | 2.18 GB/s (34.1k)
Total | 332.35 MB/s (83.0k) | 4.35 GB/s (68.0k)
| |
Block Size | 512k (IOPS) | 1m (IOPS)
------ | --- ---- | ---- ----
Read | 5.13 GB/s (10.0k) | 5.68 GB/s (5.5k)
Write | 5.40 GB/s (10.5k) | 6.06 GB/s (5.9k)
Total | 10.53 GB/s (20.5k) | 11.74 GB/s (11.4k)
Geekbench 5 Benchmark Test:
---------------------------------
Test | Value
|
Single Core | 1103
Multi Core | 1040
Full Test | https://browser.geekbench.com/v5/cpu/22351758
YABS completed in 2 min 38 sec
Command generated as: curl -sL yabs.sh | bash -s - -i -5
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
# Yet-Another-Bench-Script #
# v2024-03-05 #
# https://github.com/masonr/yet-another-bench-script #
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
Tue Mar 26 15:24:15 AST 2024
Basic System Information:
---------------------------------
Uptime : 1 days, 15 hours, 16 minutes
Processor : Intel(R) Xeon(R) CPU E5-2698 v4 @ 2.20GHz
CPU cores : 1 @ 2199.984 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM : 1.8 GiB
Swap : 2.0 GiB
Disk : 18.7 GiB
Distro : AlmaLinux 8.9 (Midnight Oncilla)
Kernel : 4.18.0-240.15.1.el8_3.x86_64
VM Type : KVM
IPv4/IPv6 : ✔ Online / ❌ Offline
IPv4 Network Information:
---------------------------------
ISP : Nexeon Technologies
ASN : AS20278 Nexeon Technologies, Inc.
Host : 365 Group
Location : Jacksonville, Florida (FL)
Country : United States
fio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/vda1):
---------------------------------
Block Size | 4k (IOPS) | 64k (IOPS)
------ | --- ---- | ---- ----
Read | 141.26 MB/s (35.3k) | 869.70 MB/s (13.5k)
Write | 141.63 MB/s (35.4k) | 874.28 MB/s (13.6k)
Total | 282.90 MB/s (70.7k) | 1.74 GB/s (27.2k)
| |
Block Size | 512k (IOPS) | 1m (IOPS)
------ | --- ---- | ---- ----
Read | 1.11 GB/s (2.1k) | 1.14 GB/s (1.1k)
Write | 1.17 GB/s (2.2k) | 1.22 GB/s (1.1k)
Total | 2.28 GB/s (4.4k) | 2.37 GB/s (2.3k)
iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider | Location (Link) | Send Speed | Recv Speed | Ping
----- | ----- | ---- | ---- | ----
Clouvider | London, UK (10G) | 358 Mbits/sec | 247 Mbits/sec | 98.2 ms
Eranium | Amsterdam, NL (10G) | 672 Mbits/sec | 188 Mbits/sec | 109 ms
Telia | Helsinki, FI (10G) | 474 Mbits/sec | 195 Mbits/sec | 136 ms
Uztelecom | Tashkent, UZ (10G) | 746 Mbits/sec | 713 Mbits/sec | 198 ms
Leaseweb | Singapore, SG (10G) | 368 Mbits/sec | 174 Mbits/sec | 222 ms
Clouvider | Los Angeles, CA, US (10G) | 450 Mbits/sec | busy | 63.4 ms
Leaseweb | NYC, NY, US (10G) | 414 Mbits/sec | 201 Mbits/sec | 30.3 ms
Edgoo | Sao Paulo, BR (1G) | 710 Mbits/sec | 203 Mbits/sec | 113 ms
Geekbench 6 Benchmark Test:
---------------------------------
Test | Value
|
Single Core | 780
Multi Core | 805
Full Test | https://browser.geekbench.com/v6/cpu/5478743
YABS completed in 18 min 51 sec