- Joined
- Aug 16, 2005
- Messages
- 24,159 (3.75/day)
- Location
- Washington
| System Name | Venslar |
|---|---|
| Processor | I9 13900ks |
| Motherboard | EVGA z690 Dark KINGPIN |
| Cooling | EK-AIO Elite 360 D-RGB |
| Memory | 64GB Gskill Trident Z5 DDR5 6000 @6400 |
| Video Card(s) | MSI SUPRIM Liquid X 4090 |
| Storage | 1x 500GB 980 Pro | 1x 1TB 980 Pro | 1x 8TB Corsair MP400 |
| Display(s) | 3x Gigabyte M28U (4k IPS) |
| Case | Lian Li o11 Evo Dynamic White |
| Audio Device(s) | Schiit Hel 2e on Moondrop Kato's |
| Power Supply | Bequiet! Power Pro 12 1500w |
| Mouse | Roccat Kone AIMO (White) |
| Keyboard | Ducky One 3 Pure White |
| VR HMD | HTC VIVE |
| Software | Windows 11 x64 Pro |
| Benchmark Scores | I dont have time for that. |
This. Its a common misconception even among jr sysadmins that you are assigning physical cores. You are not. the definition between all type 1's (proxmox, hyper-v, esxi etc) is "vCPU" the underlying schedulers are doing the rest.
No need to physically gimp and use p core only.
In this case Virtualbox is a type 2. It is using the host OS to manage all hardware interfacing. So the performance impact is theoretically linked to how well your OS handles hardware scheduling and the other things that are running on that OS.
