<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
tt
{mso-style-priority:99;
font-family:"Courier New";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Sven,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Yes, I think that fileset level include/exclude would be sufficient for us. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">It also begs the question about the same for write caching. We haven’t experimented with it yet, but are looking forward to employing HAWC for scratch-like
workloads. Do you imagine providing the same sort of HAWC bypass include/exclude to be part of this? That might be useful for excluding datasets where the write ingest rate isn’t massive and the degree of risk we’re comfortable with potential data recovery
issues in the face of complex outages may be much lower.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Paul<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> gpfsug-discuss-bounces@gpfsug.org [mailto:gpfsug-discuss-bounces@gpfsug.org]
<b>On Behalf Of </b>Sven Oehme<br>
<b>Sent:</b> Monday, June 22, 2015 7:14 PM<br>
<b>To:</b> gpfsug main discussion list<br>
<b>Subject:</b> Re: [gpfsug-discuss] LROC Express<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>Hi Paul,<br>
<br>
just out of curiosity, not that i promise anything, but would it be enough to support include/exclude per fileset level or would we need path and/or extension or even more things like owner of files as well ?
<br>
<br>
Sven<br>
<br>
------------------------------------------<br>
Sven Oehme <br>
Scalable Storage Research <br>
email: <a href="mailto:oehmes@us.ibm.com">oehmes@us.ibm.com</a> <br>
Phone: +1 (408) 824-8904 <br>
IBM Almaden Research Lab <br>
------------------------------------------<br>
<br>
<img border="0" width="16" height="16" id="_x0000_i1025" src="cid:image001.gif@01D0AD9B.CDBE95E0" alt="Inactive hide details for "Sanchez, Paul" ---06/22/2015 03:57:29 PM---I can’t confirm whether it works with Express, since we"><span style="color:#424282">"Sanchez,
Paul" ---06/22/2015 03:57:29 PM---I can’t confirm whether it works with Express, since we’re also running standard. But as a simple t</span><br>
<br>
<span style="font-size:10.0pt;color:#5F5F5F">From: </span><span style="font-size:10.0pt">"Sanchez, Paul" <<a href="mailto:Paul.Sanchez@deshaw.com">Paul.Sanchez@deshaw.com</a>></span><br>
<span style="font-size:10.0pt;color:#5F5F5F">To: </span><span style="font-size:10.0pt">gpfsug main discussion list <<a href="mailto:gpfsug-discuss@gpfsug.org">gpfsug-discuss@gpfsug.org</a>></span><br>
<span style="font-size:10.0pt;color:#5F5F5F">Date: </span><span style="font-size:10.0pt">06/22/2015 03:57 PM</span><br>
<span style="font-size:10.0pt;color:#5F5F5F">Subject: </span><span style="font-size:10.0pt">Re: [gpfsug-discuss] LROC Express</span><br>
<span style="font-size:10.0pt;color:#5F5F5F">Sent by: </span><span style="font-size:10.0pt"><a href="mailto:gpfsug-discuss-bounces@gpfsug.org">gpfsug-discuss-bounces@gpfsug.org</a></span><o:p></o:p></p>
<div class="MsoNormal">
<hr size="2" width="100%" noshade="" style="color:#8091A5" align="left">
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br>
<br>
<span style="font-family:"Calibri","sans-serif";color:#1F497D">I can’t confirm whether it works with Express, since we’re also running standard. But as a simple test, I can confirm that deleting the gpfs.ext package doesn’t seem to throw any errors w.r.t. LROC
in the logs at startup, and “mmdiag --lroc” looks normal when running without gpfs.ext (Standard Edition package). Since we have other standard edition features enabled, I couldn’t get far enough to actually test whether the LROC was still functional though.</span><br>
<br>
<span style="font-family:"Calibri","sans-serif";color:#1F497D">In the earliest 4.1.0.x releases the use of LROC was confused with “serving NSDs” and so the use of the feature required a server license, and it did throw errors at startup about that. We’ve confirmed
that in recent releases that this is no longer a limitation, and that it was indeed erroneous since the goal of LROC was pretty clearly to extend the capabilities of client-side pagepool caching.</span><br>
<br>
<span style="font-family:"Calibri","sans-serif";color:#1F497D">LROC also appears to have some rate-limiting (queue depth mgmt?) so you end up in many cases getting partial file-caching after a first read, and a subsequent read can have a mix of blocks served
from local cache and from NSD. Further reads can result in more complete local block caching of the file. One missing improvement would be to allow its use on a per-filesystem (or per-pool) basis. For instance, when backing a filesystem with a huge array of
Flash or even a GSS/ESS then the performance benefit of LROC may be negligible or even negative, depending on the performance characteristics of the local disk. But against filesystems on archival media, LROC will almost always be a win. Since we’ve started
to see features using tracked I/O access time to individual NSDs (e.g. readReplicaPolicy=fastest), there’s potential here to do something adaptive based on heuristics as well. Anyone else using this at scale and seeing a need for additional knobs?
</span><br>
<br>
<span style="font-family:"Calibri","sans-serif";color:#1F497D">Thx<br>
Paul</span><br>
<br>
<b><span style="font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-family:"Tahoma","sans-serif"">
<a href="mailto:gpfsug-discuss-bounces@gpfsug.org">gpfsug-discuss-bounces@gpfsug.org</a> [<a href="mailto:gpfsug-discuss-bounces@gpfsug.org">mailto:gpfsug-discuss-bounces@gpfsug.org</a>]
<b>On Behalf Of </b>Barry Evans<b><br>
Sent:</b> Monday, June 22, 2015 11:40 AM<b><br>
To:</b> gpfsug main discussion list<b><br>
Subject:</b> Re: [gpfsug-discuss] LROC Express</span><br>
<br>
<span style="font-size:13.5pt">Hi Bob, <br>
<br>
Thanks for this, just to confirm does this mean that it *does not* work with express?<br>
<br>
Cheers,<br>
Barry<br>
<br>
<br>
Bob Oesterlin wrote: </span><br>
<span style="font-size:13.5pt">It works with Standard edition, just make sure you have the right license for the nodes using LROC.</span><br>
<br>
<span style="font-size:13.5pt">Bob Oesterlin</span><br>
<span style="font-size:13.5pt">Nuance COmmunications</span><br>
<br>
<br>
<span style="font-size:13.5pt">Bob Oesterlin</span><br>
<br>
<br>
<span style="font-size:13.5pt">On Mon, Jun 22, 2015 at 10:28 AM, Barry Evans <</span><a href="mailto:bevans@pixitmedia.com"><span style="font-size:13.5pt">bevans@pixitmedia.com</span></a><span style="font-size:13.5pt">> wrote:</span><br>
<span style="font-size:13.5pt">Hi All,<br>
<br>
Very quick question for those in the know - does LROC require a standard license, or will it work with Express? I can't find anything in the FAQ regarding this so I presume Express is ok, but wanted to make sure.<br>
<br>
Regards,<br>
Barry Evans<br>
Technical Director<br>
Pixit Media/ArcaStream <br>
<br>
<br>
<br>
-- <br>
<br>
This email is confidential in that it is intended for the exclusive attention of the addressee(s) indicated. If you are not the intended recipient, this email should not be read or disclosed to any other person. Please notify the sender immediately and delete
this email from your computer system. Any opinions expressed are not necessarily those of the company from which this email was sent and, whilst to the best of our knowledge no viruses or defects exist, no responsibility can be accepted for any loss or damage
arising from its receipt or subsequent use of this email.<br>
_______________________________________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at </span><a href="http://gpfsug.org/"><span style="font-size:13.5pt">gpfsug.org</span></a><u><span style="font-size:13.5pt;color:blue"><br>
</span></u><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><span style="font-size:13.5pt">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</span></a><br>
<br>
<span style="font-family:"Courier New"">_______________________________________________</span><br>
<span style="font-family:"Courier New"">gpfsug-discuss mailing list</span><br>
<span style="font-family:"Courier New"">gpfsug-discuss at gpfsug.org</span><br>
<a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><span style="font-family:"Courier New"">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</span></a><br>
<br>
<br>
<span style="font-size:13.5pt">This email is confidential in that it is intended for the exclusive attention of the addressee(s) indicated. If you are not the intended recipient, this email should not be read or disclosed to any other person. Please notify
the sender immediately and delete this email from your computer system. Any opinions expressed are not necessarily those of the company from which this email was sent and, whilst to the best of our knowledge no viruses or defects exist, no responsibility can
be accepted for any loss or damage arising from its receipt or subsequent use of this email.</span><tt><span style="font-size:10.0pt">_______________________________________________</span></tt><span style="font-size:10.0pt;font-family:"Courier New""><br>
<tt>gpfsug-discuss mailing list</tt><br>
<tt>gpfsug-discuss at gpfsug.org</tt><br>
<tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></tt><br>
</span><br>
<br>
<o:p></o:p></p>
</div>
</body>
</html>