<html><body bgcolor="#FFFFFF"><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: oehmes@us.ibm.com <br>Phone: +1 (408) 824-8904 <br>IBM Almaden Research Lab <br>------------------------------------------<br><br><img width="16" height="16" src="cid:1__=07BBF4FFDFECE99A8f9e8a93df938690918c07B@" border="0" 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"><font 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</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">"Sanchez, Paul" <Paul.Sanchez@deshaw.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">gpfsug main discussion list <gpfsug-discuss@gpfsug.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">06/22/2015 03:57 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [gpfsug-discuss] LROC Express</font><br><font size="2" color="#5F5F5F">Sent by: </font><font size="2">gpfsug-discuss-bounces@gpfsug.org</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><font color="#1F497D" face="Calibri">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.</font><br><font color="#1F497D" face="Calibri"> </font><br><font color="#1F497D" face="Calibri">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.</font><br><font color="#1F497D" face="Calibri"> </font><br><font color="#1F497D" face="Calibri">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? </font><br><font color="#1F497D" face="Calibri"> </font><br><font color="#1F497D" face="Calibri">Thx<br>Paul</font><br><font color="#1F497D" face="Calibri"> </font><br><b><font face="Tahoma">From:</font></b><font face="Tahoma"> gpfsug-discuss-bounces@gpfsug.org [</font><font face="Tahoma"><a href="mailto:gpfsug-discuss-bounces@gpfsug.org">mailto:gpfsug-discuss-bounces@gpfsug.org</a></font><font face="Tahoma">] </font><b><font face="Tahoma">On Behalf Of </font></b><font face="Tahoma">Barry Evans</font><b><font face="Tahoma"><br>Sent:</font></b><font face="Tahoma"> Monday, June 22, 2015 11:40 AM</font><b><font face="Tahoma"><br>To:</font></b><font face="Tahoma"> gpfsug main discussion list</font><b><font face="Tahoma"><br>Subject:</font></b><font face="Tahoma"> Re: [gpfsug-discuss] LROC Express</font><br><font size="4" face="Times New Roman"> </font><br><font size="4" face="Times New Roman">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: </font><br><font size="4" face="Times New Roman">It works with Standard edition, just make sure you have the right license for the nodes using LROC.</font><br><font size="4" face="Times New Roman"> </font><br><font size="4" face="Times New Roman">Bob Oesterlin</font><br><font size="4" face="Times New Roman">Nuance COmmunications</font><br><font size="4" face="Times New Roman"> </font><br><font size="4" face="Times New Roman"> </font><br><font size="4" face="Times New Roman">Bob Oesterlin</font><br><font size="4" face="Times New Roman"> </font><br><font size="4" face="Times New Roman"> </font><br><font size="4" face="Times New Roman">On Mon, Jun 22, 2015 at 10:28 AM, Barry Evans <</font><a href="mailto:bevans@pixitmedia.com"><u><font size="4" color="#0000FF" face="Times New Roman">bevans@pixitmedia.com</font></u></a><font size="4" face="Times New Roman">> wrote:</font><br><font size="4" face="Times New Roman">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 </font><a href="http://gpfsug.org/"><u><font size="4" color="#0000FF" face="Times New Roman">gpfsug.org</font></u></a><u><font size="4" color="#0000FF" face="Times New Roman"><br></font></u><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><u><font size="4" color="#0000FF" face="Times New Roman">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></u></a><br><font size="4" face="Times New Roman"> </font><br><font face="Courier New">_______________________________________________</font><br><font face="Courier New">gpfsug-discuss mailing list</font><br><font face="Courier New">gpfsug-discuss at gpfsug.org</font><br><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><u><font color="#0000FF" face="Courier New">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></u></a><br><font size="4" face="Times New Roman"> </font><br><br><font size="4" face="Times New Roman">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.</font><tt>_______________________________________________<br>gpfsug-discuss mailing list<br>gpfsug-discuss at gpfsug.org<br></tt><tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss">http://gpfsug.org/mailman/listinfo/gpfsug-discuss</a></tt><tt><br></tt><br><br><BR>
</body></html>