Lavalink uses 1 core when i have 4.
See original GitHub issueDescription
Lavalink uses 1 core when i have 4.
Version info
Client used: Doesnt matter?
Output of java -version
:
Im using java adopt@1.13.0-2
2021-07-19 10:25:13.186 INFO 137633 --- [ main] o.s.b.w.e.u.UndertowServletWebServer : Undertow started on port(s) 1441 (http) with context path ''
2021-07-19 10:25:13.190 INFO 137633 --- [ main] lavalink.server.Launcher : Started Launcher in 2.535 seconds (JVM running for 2.91)
2021-07-19 10:25:13.191 INFO 137633 --- [ main] lavalink.server.Launcher : You can safely ignore the big red warning about illegal reflection. See https://github.com/Frederikam/Lavalink/issues/295
2021-07-19 10:26:29.269 INFO 137633 --- [ XNIO-1 task-1] io.undertow.servlet : Initializing Spring DispatcherServlet 'dispatcherServlet'
2021-07-19 10:26:29.270 INFO 137633 --- [ XNIO-1 task-1] o.s.web.servlet.DispatcherServlet : Initializing Servlet 'dispatcherServlet'
2021-07-19 10:26:29.276 INFO 137633 --- [ XNIO-1 task-1] o.s.web.servlet.DispatcherServlet : Completed initialization in 6 ms
2021-07-19 10:26:29.295 INFO 137633 --- [ XNIO-1 task-1] l.server.io.HandshakeInterceptorImpl : Incoming connection from /3.86.7.221:43616
2021-07-19 10:26:29.358 INFO 137633 --- [ XNIO-1 task-1] lavalink.server.io.SocketServer : Connection successfully established from /hehe boi
2021-07-19 10:26:29.365 ERROR 137633 --- [pool-1-thread-1] o.h.p.linux.LinuxCentralProcessor : Couldn't find physical processor count. Assuming 1.
2021-07-19 10:26:29.366 ERROR 137633 --- [pool-1-thread-1] o.h.p.linux.LinuxCentralProcessor : Couldn't find physical package count. Assuming 1.
Output of lscpu:
Architecture: aarch64
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per cluster: 4
Socket(s): -
Cluster(s): 1
NUMA node(s): 1
Vendor ID: ARM
Model: 1
Model name: Neoverse-N1
Stepping: r3p1
BogoMIPS: 50.00
NUMA node0 CPU(s): 0-3
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Lavalink/README.md at master - GitHub
A standalone audio sending node based on Lavaplayer and Koe. Allows for sending audio without it ever reaching any of your shards. Being...
Read more >lavalink - npm
A Javascript wrapper for the Lavalink audio client for Discord. Only supports Lavalink v3; use 0.7.x for Lavalink v2.
Read more >The challenge of running lavalink | Darren Nathanael
Currently, I have three nodes running; those are equipped with 16 GB ram and a six-core processor. And I have one HAProxy instance...
Read more >Lavalink Setup | Corebot Documentation
Lavalink is a standalone audio sending node based on Lavaplayer and JDA-Audio. Allows for sending audio without it ever reaching any of your...
Read more >Only one core/thread pinned at 100% usage | Windows Bug Fix
Using Windows, but you've noticed sluggish performance, or have just one core running at 100% no matter what? This video shows you how...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Just some info in case someone else comes across this issue at some point… this should have been fixed in one of the oshi updates that was done in the last couple of years and I recall doing some testing on a Raspberry pi regarding it, and I am under the impression that this has been resolved.
official support for arm has been added in the meantime I don’t know if the cpu stats are accurate now but if they aren’t feel free to reopen this issue