gea...
speaking of interrupts.. this is interesting...
on this rebuild using 151022.. updated
I get gigabit wire lan max speeds from napp-it SMB into a mac os host.. over 100MB/s typical.. and napp-it shows about 10k interrupts
the transfer is pretty flat and not spikey.. I would call it excellent sustained transfers over 5GB files etc..
when I take a large file or set of files and SEND them into napp-it... I get between half and 3/4 speed.. call it on avg 55MB/s to 70MB/s but interrupts are off the chart like 25,000 or more.. so the ominos/napp-it VM is generating roughly double the interrupts for roughly 1/2 to 2/3 the speed?
I am using the standard image, and the SMB connection is through the physical intel 1GB port on the intel motherboard, and the napp-it VM using the standard E1000 interface. I used you standard tuning which I believe only tunes the vmxnet3 interface for TSO .. should I need to adjust the E1000 similarly ... I am no DTRACE wizard so I have been unable to zero into which process is the culprit
also, the disks at both ends are capable of sustained writing well in excess of 300MBs so its not that.. and napp-it graphs only show ~30-40% wait or busy on the pool during the write. NAPP-IT does fill about 8GB of the 10GB the VM has allocated to it during the write to the box, as well as during download ops.. it seems to release it right away.. actually memory use seem pretty stable on this release.
napp-it is given 4 vCPU and 10GB memory.
during heavy up/down link activity... cpu seems capped right at 50%.. I am guessing whatever is the bottle neck is single threaded?
thoughts?
speaking of interrupts.. this is interesting...
on this rebuild using 151022.. updated
I get gigabit wire lan max speeds from napp-it SMB into a mac os host.. over 100MB/s typical.. and napp-it shows about 10k interrupts
the transfer is pretty flat and not spikey.. I would call it excellent sustained transfers over 5GB files etc..
when I take a large file or set of files and SEND them into napp-it... I get between half and 3/4 speed.. call it on avg 55MB/s to 70MB/s but interrupts are off the chart like 25,000 or more.. so the ominos/napp-it VM is generating roughly double the interrupts for roughly 1/2 to 2/3 the speed?
I am using the standard image, and the SMB connection is through the physical intel 1GB port on the intel motherboard, and the napp-it VM using the standard E1000 interface. I used you standard tuning which I believe only tunes the vmxnet3 interface for TSO .. should I need to adjust the E1000 similarly ... I am no DTRACE wizard so I have been unable to zero into which process is the culprit
also, the disks at both ends are capable of sustained writing well in excess of 300MBs so its not that.. and napp-it graphs only show ~30-40% wait or busy on the pool during the write. NAPP-IT does fill about 8GB of the 10GB the VM has allocated to it during the write to the box, as well as during download ops.. it seems to release it right away.. actually memory use seem pretty stable on this release.
napp-it is given 4 vCPU and 10GB memory.
during heavy up/down link activity... cpu seems capped right at 50%.. I am guessing whatever is the bottle neck is single threaded?
thoughts?