Update Proxmox VM specifications and optimize deployment configurations
- Revised CPU and memory specifications for various VMs, moving high-resource workloads from ML110-01 to R630-01 to balance resource allocation. - Updated deployment YAML files to reflect changes in node assignments, CPU counts, and storage types, transitioning to Ceph storage for improved performance. - Enhanced documentation to clarify resource usage and deployment strategies, ensuring efficient utilization of available hardware.
This commit is contained in:
@@ -17,13 +17,13 @@ This document provides a comprehensive inventory of all Proxmox VE hardware in t
|
||||
|----------|-------|-----------|----------------------------|-------------|
|
||||
| **Total Systems** | 16 | 2,304 GB | 34+ cores (validated) | 2 |
|
||||
| **HPE ML110 Gen9** | 1 | 256 GB | 6 cores | 0 |
|
||||
| **Dell R630 (High Memory)** | 1 | 768 GB | 28 cores (56 threads) | 0 |
|
||||
| **Dell R630 (High Memory)** | 1 | 768 GB | 52 cores (104 threads) | 0 |
|
||||
| **Dell R630 (Standard)** | 12 | 1,536 GB | ~260-390 cores (est.) | 0 |
|
||||
| **Dell Precision 7920** | 2 | 192 GB | ~32-64 cores (est.) | 2 |
|
||||
|
||||
**Note**:
|
||||
- ✅ HPE ML110 Gen9: Validated (6 cores)
|
||||
- ✅ Dell R630 (High Memory): Validated (28 cores, 56 threads)
|
||||
- ✅ Dell R630 (High Memory): Validated (52 cores, 104 threads)
|
||||
- ⏳ Dell R630 (Standard): Estimates based on typical configurations
|
||||
- ⏳ Dell Precision 7920: Estimates based on typical configurations
|
||||
|
||||
@@ -162,18 +162,18 @@ This document provides a comprehensive inventory of all Proxmox VE hardware in t
|
||||
**Processor**:
|
||||
- **CPU Model**: Intel Xeon E5-2660 v4 @ 2.00GHz
|
||||
- **CPU Count**: 2 processors (dual socket)
|
||||
- **CPU Cores**: 14 cores per processor (28 total cores)
|
||||
- **CPU Threads**: 28 threads per processor (56 total threads with hyperthreading)
|
||||
- **CPU Cores**: 26 cores per processor (52 total cores)
|
||||
- **CPU Threads**: 26 threads per processor (104 total threads with hyperthreading)
|
||||
- **CPU Architecture**: x86_64 (Broadwell-EP)
|
||||
- **CPU Speed**: 2.00 GHz (Base), 1.20-3.20 GHz (Range, Turbo up to 3.20 GHz)
|
||||
- **CPU Stepping**: 1
|
||||
- **Virtualization**: Intel VT-x (VMX), VT-d supported
|
||||
- **NUMA**: 2 NUMA nodes (one per CPU socket)
|
||||
- **Cache**:
|
||||
- L1d: 896 KiB (28 instances)
|
||||
- L1i: 896 KiB (28 instances)
|
||||
- L2: 7 MiB (28 instances)
|
||||
- L3: 70 MiB (2 instances, 35 MiB per socket)
|
||||
- L1d: 1,664 KiB (52 instances)
|
||||
- L1i: 1,664 KiB (52 instances)
|
||||
- L2: 13 MiB (52 instances)
|
||||
- L3: 130 MiB (2 instances, 65 MiB per socket)
|
||||
|
||||
**Memory**:
|
||||
- **Total RAM**: 768 GB (755 GiB usable, 792 GB total including system overhead)
|
||||
@@ -245,7 +245,7 @@ This document provides a comprehensive inventory of all Proxmox VE hardware in t
|
||||
- **Network**: vmbr0 bridge configured with static IP (192.168.11.11/24)
|
||||
- **VMs Running**: Multiple VMs configured (VMIDs: 101, 104, 134, 137, 138, 144, 148)
|
||||
- **Ceph**: Ceph OSD configured on secondary disk
|
||||
- **CPU Utilization**: 56 logical CPUs available (28 cores × 2 sockets with hyperthreading)
|
||||
- **CPU Utilization**: 104 logical CPUs available (52 cores × 2 sockets with hyperthreading)
|
||||
- **Memory Utilization**: ~744 GB available for VMs
|
||||
|
||||
**Deployment Notes**:
|
||||
@@ -254,7 +254,7 @@ This document provides a comprehensive inventory of all Proxmox VE hardware in t
|
||||
- Excellent for Proxmox VE cluster node
|
||||
- Can host many VMs with high memory requirements
|
||||
- Consider for primary compute node in cluster
|
||||
- **CPU**: 28 cores (56 threads) provides excellent compute capacity
|
||||
- **CPU**: 52 cores (104 threads) provides excellent compute capacity
|
||||
- **Memory**: 768 GB provides excellent capacity for memory-intensive workloads
|
||||
- **Storage**: Hardware RAID controller available (PERC H730 Mini)
|
||||
- **Network**: 10GbE capable - consider configuring additional ports for better performance
|
||||
|
||||
Reference in New Issue
Block a user