The CPUSPEED of system stats in aux_stats$ shows 342 for that emulated machine (342 millions of instructions per second). With t as ( select rownum from dual connect by level The emulated VM is 13.75 times slowerģ.) CPUSPEED in the Oracle system statistics To utilize a DB sever on CPU I usually run the following cpu_load.sql-script in sqlplus: set lines 120 REMARK: All tests performed for this Blog were done on those 2 machines (MacBook Air 2020 M1 with emulated UTM-VM versus MacBook Pro 2019 Intel with Virtualbox). Result: Emulated VM with half the cores is approx factor 18 slower than on the native machine. I did run the same on a virtualbox on a MacBook Pro with a 2.6 GHZ Core i7:Ģ Cores for VM on type 2 hypervisor on native x86_64: Patch PDB$SEED and PDB1: 1h, 41min, 30sec.This test was performed with “Force Multicore” disabled.ġ Core for the VM on the emulated environment: But I wanted to know exact numbers, so I did a couple of tests:ġ.) Running datapatch against a CDB with 1 PDB (part of dbca after installing 19.16. It takes considerable more time to install the environment and it of course feels much slower than running a type 2 hypervisor (like Virtualbox on native x86_64). Now to the main question: What is the performance of the DB-server running in the emulated UTM-VM? I had to disable cores then to make Java work (see the summary below on how I did that). In my case that was fast, but running Java in the VM did not work anymore. With “Force Multicore” enabled more than 1 Core can be used from the Mac on the VM. In that case UTM can only use 1 core of the Mac. Everything runs very stable as long as the UTM System setting “Force Multicore” is not enabled. from Turing Software LLC (can be downloaded from the App Store) and costs $10įirst of all the good news is that I could install and run the 2 environments without any crash. I thought I’ll check that myself on what “very slow” means in terms of running an Oracle database in an emulated environment. The product UTM makes that easy as it adds a GUI on top of QEMU.Īccording lots of feedback on the internet the emulation is VERY SLOW. over VPN)Īnother potential alternative would be the emulation of x86-64 on ARM. So you need to carry the hardware with you or provide remote access to it, e.g. running the DB-server on separate hardware (requires access to separate hardware.runinng the DB-server VM on the Cloud (requires access to the cloud resources over the internet).REMARK: Oracle announced to port the DB software to ARM in the future. a Consultant with an Apple Laptop to be able to run tests against Oracle databases on that Laptop. as the Oracle Database does not run on ARM, a workaround is necessary for e.g. on Apple MacBook Pros with M1 or M2 processors). ARM architecture), it’s no longer possible to run VMs based on Intel x86-64 on Apple ARM (e.g. Since Apple moved to its own processor type (Apple Silicon, i.e. For testing purposes many IT-people traditionally use Virtual Machines (VMs) on their Laptops (often on Oracle Virtualbox).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |