One though I have is if you can figure out which core is being maxed out then turn off its hyperthread. On the single cpu speed benchmarks I have ran turning off the shared idle hyperthread gains several % on cpu bound benchmarks. If the hyperthread is being actively used by some other process then it should gain quite a bit more. You may also want to run turbostat and verify that the processor in question is running full speed and/or turboboosting (it probably is if everything is working right). On Tue, Feb 19, 2019 at 5:33 PM Roy Sigurd Karlsbakk <roy@xxxxxxxxxxxxx> wrote: > > > Is this process going to be running all of the time, or just run for a > > few minutes/hours at a time? If for a few minutes at a time you may > > want to use a raid0 ssd array for the data collection and then have > > another process to move that data onto the raid6. If the data is > > split multiple files (a few gb each) then the backend process can move > > the finished files just behind the main process and if the files are > > small enough then they will still be in file cache and you won't have > > to read off of the ssd array, and you will be isolated from random > > blips on the spinning disks. Give you are talking about 12 disks, if > > one of those spinning disk blips it will be whatever timeout you set > > on the disk assuming you have a disk that allows the timeout to be set > > (the lowest I have found for that timeout is 0.1seconds). > > He did use SSDs to check this, with RAID-6, and the performance issue was the same, CPU-bound > > Vennlig hilsen > > roy > -- > Roy Sigurd Karlsbakk > (+47) 98013356 > http://blogg.karlsbakk.net/ > GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt > -- > Hið góða skaltu í stein höggva, hið illa í snjó rita. >
