- Joined
- Aug 16, 2005
- Messages
- 27,610 (3.84/day)
- Location
- Alabama
| System Name | RogueOne |
|---|---|
| Processor | Xeon W9-3495x |
| Motherboard | ASUS w790E Sage SE |
| Cooling | SilverStone XE360-4677 |
| Memory | 128gb Gskill Zeta R5 DDR5 RDIMMs |
| Video Card(s) | MSI SUPRIM Liquid 5090 |
| Storage | 1x 2TB WD SN850X | 2x 8TB GAMMIX S70 |
| Display(s) | 49" Philips Evnia OLED (49M2C8900) |
| Case | Thermaltake Core P3 Pro Snow |
| Audio Device(s) | Moondrop S8's on chitt Gunnr |
| Power Supply | Seasonic Prime TX-1600 |
| Mouse | Razer Viper mini signature edition (mercury white) |
| Keyboard | Wooting 80 HE White, Gateron Jades |
| VR HMD | Quest 3 |
| Software | Windows 11 Pro Workstation |
| 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.
