- Joined
- Jan 3, 2021
- Messages
- 3,438 (2.45/day)
- Location
- Slovenia
Processor | i5-6600K |
---|---|
Motherboard | Asus Z170A |
Cooling | some cheap Cooler Master Hyper 103 or similar |
Memory | 16GB DDR4-2400 |
Video Card(s) | IGP |
Storage | Samsung 850 EVO 250GB |
Display(s) | 2x Oldell 24" 1920x1200 |
Case | Bitfenix Nova white windowless non-mesh |
Audio Device(s) | E-mu 1212m PCI |
Power Supply | Seasonic G-360 |
Mouse | Logitech Marble trackball, never had a mouse |
Keyboard | Key Tronic KT2000, no Win key because 1994 |
Software | Oldwin |
Not AL specific. I wanted to point out that the nasty scenario you mentioned is very much possible when all cores are equal, if you have HT.Well, that wouldn't be an AL specific problem (were we talking AL? I lost track).
Fwiw, I've always been wondering whether batching threads that do light work (as opposed to spreading them across as many execution units the CPU presents) is a pro or a con. I still haven't been able to figure that out.
I'd like to see more testing with, for example, 2-, 4- and 8-thread compiling on P cores with HT vs. E cores. Results for ST indicate that E performance is about 2/3 of P performance. It would be very interesting to see how this scales. Two E cores about the same as one P core?
Not all day long but maybe for minutes on end, if you have a development machine and full software stack on it.You're probably not hammering MySQL all day long a desktop, so an E core is the perfect place for it to loiter. Of course, we'd want that load to move to a P-thread as soon as it starts to, you know, work. A damn good example of a workload that's not that easy to figure out, thank you very much.