July 2, 20179 yr On a test server (dl380 g6 dual e5520 16gb ecc ram) I have running 6.4.0-rc6, it seems like using the emulator pin pegs the assigned core to 100% or near that for usage. Anyone stumble across that? And now I'll explain how weirdly it is setup. Core 0 is the only core unRaid gets to use. The remaining 15 are reserved for the vm which does network transcoding. The array has 1 disk in it hosting the vm, no parity. No dockers, or plugins causing added use. On 6.2.4 using this configuration, emulator pin set to core 0 only added 10-25% usage on core 0, which normally idles at 2-11% with no load. I know, don't do this, give unRaid more than 1 thread. But it really doesn't need it if it isn't doing anything but hosting a single vm. YES there are other programs that can do that and I don't care. As I said, it's a test server. I'm just curios and mentioning this now because when my other servers migrate over to the stable 6.4 release that are more traditionally setup in their thread assignments, are they going to see the same issues with assigned emulator cores. So I thought I would ask. Thanks for reading.
Archived
This topic is now archived and is closed to further replies.