2017-04-25 9:03 GMT+02:00 Xavier Hernandez :
> Hi Ingard,
>
> On 24/04/17 14:43, Ingard Mevåg wrote:
>
>> I've done some more testing with tc and introduced latency on one of my
>> testservers. With 9ms latency artificially introduced using tc ( sudo tc
>> qdisc add dev
Hi Ingard,
On 24/04/17 14:43, Ingard Mevåg wrote:
I've done some more testing with tc and introduced latency on one of my
testservers. With 9ms latency artificially introduced using tc ( sudo tc
qdisc add dev bond0 root netem delay 9ms ) to a testserver in the same
DC as the disperse volume
I've done some more testing with tc and introduced latency on one of my
testservers. With 9ms latency artificially introduced using tc ( sudo tc
qdisc add dev bond0 root netem delay 9ms ) to a testserver in the same DC
as the disperse volume servers I get more or less the same throughput as I
do
+Ashish
Ashish,
Could you help Ingard? Do let me know what you find.
On Mon, Apr 24, 2017 at 4:50 PM, Ingard Mevåg wrote:
> Hi. I can't see a fuse thread at all. Please see attached screenshot of
> top process with threads. Keep in mind this is from inside the
On Mon, Apr 24, 2017 at 3:47 PM, Pranith Kumar Karampuri <
pkara...@redhat.com> wrote:
> We were able to saturate hardware with EC as well. Could you check 'top'
> in threaded mode to see if fuse thread is saturated when you run dd?
>
This is for mount process by the way.
>
> On Mon, Apr 24,
We were able to saturate hardware with EC as well. Could you check 'top' in
threaded mode to see if fuse thread is saturated when you run dd?
On Mon, Apr 24, 2017 at 3:27 PM, Ingard Mevåg wrote:
> Hi
> I've been playing with disperse volumes the past week, and so far i can
>
Hi
I've been playing with disperse volumes the past week, and so far i can not
get more than 12MB/s when i do a write test. I've tried a distributed
volume on the same bricks and gotten close to gigabit speeds. iperf
confirms gigabit speeds to all three servers in the storage pool.
The three