<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 12/21/2015 02:26 PM, Mateusz
Zajakala wrote:<br>
</div>
<blockquote
cite="mid:CAEmqMM92id9mx=WmTQT-FLtQ_mbZnMNOGXft6MOFU4Bva2WBJg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>
<div>
<div>Pranith,<br>
<br>
</div>
that sounds good, Option to configure relative priorities
of READ and WRITE operations would be probably sufficient
in my case (as long as it really affects the operations
throughput). <br>
<br>
</div>
But what if you wanted to differentiate write/read
priorities from different clients? maybe it's worth thinking
about some way to enable this?</div>
</div>
</div>
</blockquote>
<br>
Oh, these options will be on server side. So all clients will see
same priorities. That is probably the reason why the Original
developer didn't allow these priorities to be changed. I am not sure
how we can configure in a generic way. Any thoughts?<br>
<br>
Pranith<br>
<br>
<blockquote
cite="mid:CAEmqMM92id9mx=WmTQT-FLtQ_mbZnMNOGXft6MOFU4Bva2WBJg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div> <br>
<br>
</div>
Thanks!<br>
</div>
Mat<br>
<div>
<div>
<div>
<div><br>
<br>
</div>
</div>
</div>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Dec 21, 2015 at 5:00 AM,
Pranith Kumar Karampuri <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:pkarampu@redhat.com"
target="_blank">pkarampu@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class=""> <br>
<br>
<div>On 12/21/2015 02:28 AM, Mateusz Zajakala wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>
<div>Hi,<br>
<br>
</div>
<div>I have a question about ways to control/shape
IO traffic to gluster volumes.<br>
</div>
<div><br>
</div>
I have the following setup:gluster 3.7.6,
distributed/disperse volume (20 HDD bricks,
disperse 5, redundancy 1), mount points via
glusterfs fuse.<br>
<br>
</div>
<div>I have multiple read sessions (hundreds of
clients reading sequentially large >1GB files)
and multiple write sessions writing such files.
While I care that read sessions proceed with
maximum speed I can get from my HDDs, I can live
with the fact that write (archiving) sessions will
give way and proceed more slowly. <br>
<br>
</div>
<div>Is there a way to throttle write sessions?
Ideally I'd like them to have lower priority than
read sessions, but also not be limited in case
there are no read sessions at the moment. It seems
like I need some "ionice" couterpart for gusterfs.<br>
<br>
</div>
<div>Does is exist? I was wondering if this could be
achieved by tweaking "ionice" values on the client
side for writes and reads, but since clients only
use glusterfs fuse mountpoint I don't think it
would work... ?<br>
</div>
</div>
</blockquote>
</span> hi Mat,<br>
I just checked io-threads code (This feature
decides priority of different operations and multiple
threads execute the operations.), Both READ and WRITE are
in same priority. May be we can give an option to
configure this? Would you like that? I will discuss this
more on gluster-devel to see what others have to say
before coming to a conclusion about how to go about this.
Your feedback is much welcome.<br>
<br>
Pranith<br>
<blockquote type="cite">
<div dir="ltr">
<div><br>
</div>
<div>Thanks<br>
</div>
<div>Mat<br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Gluster-users mailing list
<a moz-do-not-send="true" href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>
<a moz-do-not-send="true" href="http://www.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a></pre>
</blockquote>
<br>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
</body>
</html>