[gpfsug-discuss] limit / fair share of GPFS bandwidth

[John Hearns]

Hello Egonle.   I looked at this scenario recently (H Mark!)
Maybe you could send me an email off-list?

From: gpfsug-discuss-bounces at spectrumscale.org [mailto:gpfsug-discuss-bounces at spectrumscale.org] On Behalf Of Marc A Kaplan
Sent: Sunday, January 28, 2018 4:54 PM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: Re: [gpfsug-discuss] limit / fair share of GPFS bandwidth

Depends...  While the current version of mmchqos is primarily geared towards controlling "maintenance" tasks.

It can be used to limit  (cap) the IOP rate for IOs coming from a particular GFPFS client node.

You would need a version that supports the -N option on the mmchqos command and then configure each node that will mount the FS.

Caution: try some experiments on a test system -- incorrect configuration can severely impact performance to the point where it can appear that things are totally "stuck"!   mmchqos FS --disable  --reset  should get you back to the default config for gpfs/QOS.



From:        "Eg. Bo." <egonle at aim.com<mailto:egonle at aim.com>>
To:        gpfsug-discuss at spectrumscale.org<mailto:gpfsug-discuss at spectrumscale.org>
Date:        01/27/2018 12:23 PM
Subject:        [gpfsug-discuss] limit / fair share of GPFS bandwidth
Sent by:        gpfsug-discuss-bounces at spectrumscale.org<mailto:gpfsug-discuss-bounces at spectrumscale.org>
________________________________



Hello,

 while operating a GPFS filesystem for HPC some workload of few clients is able to eat available storage and NSD performance. Compute Nodes and NSD servers are connected to Infiniband. This question somehow is weird but is there a way to limit performance / I/O / bandwidth consumption for nodes so that other node still get "good" performance?


Thanks,

 Eg. Bo. egonle at aim.com<mailto:egonle at aim.com>_______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=cvpnBBH0j41aQy0RPiG2xRL_M8mTc1izuQD3_PmtjZ8&m=r0AtLTBmDo_uZhIdntBO8k2-1Alg_2LBLPoJamV-zsY&s=BXGAuET7K4UhA24P72F4YRsAdcdJR3H02gqGOERENlE&e=<https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttp-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss%26d%3DDwICAg%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3DcvpnBBH0j41aQy0RPiG2xRL_M8mTc1izuQD3_PmtjZ8%26m%3Dr0AtLTBmDo_uZhIdntBO8k2-1Alg_2LBLPoJamV-zsY%26s%3DBXGAuET7K4UhA24P72F4YRsAdcdJR3H02gqGOERENlE%26e%3D&data=01%7C01%7Cjohn.hearns%40asml.com%7C46150883736642014bb408d566676805%7Caf73baa8f5944eb2a39d93e96cad61fc%7C1&sdata=rZq4E4Mn0RBnYdQzFOi44kSOGit2ymYDzsjc7QQrF%2Bo%3D&reserved=0>


-- The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. Unless explicitly stated otherwise in the body of this communication or the attachment thereto (if any), the information is provided on an AS-IS basis without any express or implied warranties or liabilities. To the extent you are relying on this information, you are doing so at your own risk. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. Neither the sender nor the company/group of companies he or she represents shall be liable for the proper and complete transmission of the information contained in this communication, or for any delay in its receipt.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20180129/c1cbe462/attachment.htm>