01-19-2023, 09:45 PM
(01-17-2023, 05:43 PM)mnrvovrfc Wrote:(01-17-2023, 12:20 PM)daivdW2 Wrote: It held a steady 15% CPU and just over 3.2 GB Ram. When executing the program (Running the bas file) , the CPU would go to 60% and drop back down again as soon as the program exited.
This is entirely expected from any program entering and exiting, but only that. The fault might be with the task manager trying to measure things while another program is trying to set up (race conditions and other high-technical working stuff).
The problem seems to be that you're also running the web browser, that is a big culprit of performance. If not then why do the filenames of the screenshots begin with "msedge"? If it's possible make sure no other programs are running except QB64PE and the task manager, then try these tests again.
There were no web browsers running on the VMs. Only the OS, QB64PE and the RDP Service for remote access to the VM. The screenshots are labelled by the capture program which is called ShareX.
ShareX is a tool on my Windows 11 laptop that I use to RDP into the VMs.
ProxMox is a Hypervisor. It runs on my mini server and is the tool used to manage the VMs. It has a Web based admin panel and this is the source of the graphs.
I have multiple screens so I can work on the VM using RDP to load QB64PE while watching the ProxMox stats.
I hope that makes sense?