glc001

Thanks for the input, it's much appreciated! So far it's working very well, with the only minor exception being a few hiccups while playing witcher 3 (very cpu intensive game). I'll leave it as is and revisit the issue when I upgrade my graphics card if I feel like I'm being limited by only having 3 cores.

Hi all- I recently upgraded my unraid server to allow for more robust plex transcoding, gaming etc. The gridrunner videos were enormously useful. As things have evolved, I use it almost exclusively for gaming at this point. My current setup is: xeon e3-1245 v6 (4 cores) 16 gb ecc ram gtx 1060 windows 10 VM installed on separate nvme drive which has 3 cores (core 1-3; core 0 used by unraid) and 12 gb allocated to it My question is how I can I configure unraid and the VM to maximize gaming performance? Should I assign all 4 cores to the VM? If so does it make a difference to bind unraid processes to a higher core? For what it's worth the server is NEVER used for gaming and plex transcoding simultaneously. I'm inclined to keep it as unraid with windows as a VM since I occasionally use it as a media server, but would it be a significant improvement to just install win 10 natively to allow it to access the full 4 cores and 16 gb, then just set up the media server through windows? Any thoughts are appreciated!

hmm, since i don't have the know how to upgrade to a newer linux kernel myself, i guess i'll just have to decide whether i should wait for unraid to adopt the newer kernel or just get a new motherboard...

so i have a quick question about wake on lan functionality with my unraid server... just as some quick background, i'm new to unraid and using version 4.5 beta 6 with an ecs a740gm-m mobo. unraid boots just fine without issues. i can telnet in and on every boot up, ethtool tells me that wol is disabled. so if i enable it and then put the computer to sleep (via telnet with "echo 3 >/proc/acpi/sleep"), it wakes up without any problems using a magic packet. then it gets confusing. after waking back up, ethtool tells me that wol is still enabled, but if i put the computer back to sleep, it does NOT wake up using a magic packet (even if i "re-enable" wol through ethtool prior to putting it back to sleep). so basically, if i boot up from it being completely off and then put the server to sleep, it will wake up. but if i start from a sleep state, put it to sleep and try to wake it up, it will not wake up. i'm a linux novice, so it's possible that it's something totally obvious that i'm just missing. any ideas? thanks in advance!!