![]() ![]() ![]() Virtual Box basically doesn't work due to terrible storage performance. Hyper-V doesn't work due to inability to pass through USB devices (with GUID) I attempted to run Unraid under a Type 2 Hypervisor and below is the short summary (TL DR: it's not recommended). This is incredibly annoying under heavy IO. ZFS (as of ) has a bug which causes it to not respect isolcpus. Likes: Pretty much take anything thrown at it and spit it output in my face.įuture Plans: Move to a smaller case (Raijintek Thetis?) for a more compact built.ītrfs can do snapshot! With a bit of scripting, you can achieve what znapzend does for ZFS. Primary Use: Main video/photo editing workstation + various unRAID stuff that people do on unRAID Unassigned offline backup / decommissioned: 10TB Seagate Ironwolf NAS, 8TB Seagate Ironwolf NAS, 8TB Hitachi HE8, 5TB Seagate BarraCuda 2.5" SMR, 2TB Samsung 850 Evo, 2050GB Crucial MX300, 512GB Samsung SM951 M.2 (AHCI variety) VM-only: 2x Intel Optane 905p 960GB (U.2 2.5"), Intel Optane 905p 380GB (M.2 22110) + 3x Samsung PM983 3.84TB (via Asus Hyper M.2 X16 card + split PCIe to x4,x4,x4,x4)įlash backup: Samsung FIT Plus 64GB (for rapid recovery in case main stick fails) Parity Drive: None because I trust the cloud GPU: Zotac GTX 1070 Mini for main VM, Zotac GT 710 PCIe x1 for unRAID, Nvidia Quadro P2000 for unRAID + transcoding Power Supply: Corsair HX850 (10+ years old!) RAM: 64GB Corsair Vengeance LPX 2666MHz + 32GB GSkill Ripjaw 4 2800MHz (nicked from the old workstation)Ĭase: Silverstone Fortress FT02 (old workstation case)ĭrive Cage: Evercool Dual (2x5.25 -> 3x3.5 with 80mm fan) - need this to mount 4x2.5" drives Motherboard: Gigabyte X399 Designare EX (F12e BIOS) ![]() Heatsink: Noctua NH-U14S TR4-SP3 (in push-pull - I nicked a 15mm fan from my old NH-D14 workstation cooler) OS Current: 6.9.0-beta25 (ich777 build ZFS + Nvidia) ![]() The 2990WX came out at just the right price point that makes the idea possible. I had a i7-5820K (overclocked to 4GHz) and a Xeon E3-1245v5 server (ITX case) but it was more out of necessity since I wasn't able to afford Dual Xeon to merge them and still have sufficient performance. I finally pulled the plug when Amazon finally has my motherboard in stock. I used a program called Process Lasso to get this information.After a few months of researching, prepping my data, persuading she-who-must-be-obeyed, etc. Each core runs at about 40-50% and the overall CPU usage also remains in that range. The cause of the problem seems to be that the Threadripper uses all cores but does not push them to the extreme. Without this it would actually be slower than the Haswell. I found out that if I disable SMT and work with only 16(as opposed to 32) logical cores the Threadripper does better. There is something about a "heavy" application that the Threadripper does not seem to handle that well. But for the complex application I am developing the two are roughly equivalent. The two systems execute parallelized code at approximately the same speed.Īctually the Threadripper is much faster than the Haswell when running some simple parallelized F# programs I wrote for testing purposes. I was expecting the performance of parallelized code would be much faster than under my old system with an Intel i7 4770K (Haswell processor), which has only four cores. It is very easy to write parallelized code in F# (as in any functional language) and that is essential for the application I am developing. I use the PC mostly to program in the F# language. The system is running well and is very responsive. I built a PC with an AMD Threadripper 1950X, which has 16 cores. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |