Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Autotuning on 3.4?

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Autotuning on 3.4?


Chronological Thread 
  • From: Roderick Mooi <>
  • To: Aaron Brown <>
  • Cc: perfsonar-user <>
  • Subject: Re: [perfsonar-user] Autotuning on 3.4?
  • Date: Tue, 3 Feb 2015 07:52:29 +0200

Hi Aaron

Thanks, that seems to be working.

PS I had to manually specify the file to patch as follows:

[root@perfsonar4
~]# patch -p1 -d /opt/perfsonar_ps/toolkit -i
/home/rmooi/toolkit_window_size_fix.patch
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/Shared/lib/perfSONAR_PS/NPToolkit/Config/RegularTesting.pm
b/Shared/lib/perfSONAR_PS/NPToolkit/Config/RegularTesting.pm
|index 77911ba..f9befc8 100644
|--- a/Shared/lib/perfSONAR_PS/NPToolkit/Config/RegularTesting.pm
|+++ b/Shared/lib/perfSONAR_PS/NPToolkit/Config/RegularTesting.pm
--------------------------
File to patch:
/opt/perfsonar_ps/toolkit/lib/perfSONAR_PS/NPToolkit/Config/RegularTesting.pm
patching file
/opt/perfsonar_ps/toolkit/lib/perfSONAR_PS/NPToolkit/Config/RegularTesting.pm
Hunk #1 succeeded at 1248 (offset -4 lines).
[root@perfsonar4
~]#

I’m not very familiar with the “patch” syntax but I guess this can be fixed
by modifying the command below…

Regards,

Roderick

> On 02 Feb 2015, at 5:44 PM, Aaron Brown
> <>
> wrote:
>
> Hey Roderick,
>
> Looks like an oversight, can you try applying this patch to see if it fixes
> the issue: http://ndb1.internet2.edu/~aaron/toolkit_window_size_fix.patch
>
> You can apply it by doing:
>
> patch -p1 -d /opt/perfsonar_ps/toolkit -i
> /path/to/toolkit_window_size_fix.patch
>
> Cheers,
> Aaron
>
>> On Feb 2, 2015, at 4:50 AM, Roderick Mooi
>> <>
>> wrote:
>>
>> Good day
>>
>> We are busy migrating our 3.3 nodes to 3.4.
>>
>> When I configure throughput tests I want to use Autotuning = off and
>> specify the window size (the auto-tuning gives us sub-optimal
>> measurements). So I do this in the GUI and save the tests. When I check
>> the bwctl processes, the -W doesn’t appear. Reloading the scheduled tests
>> page shows autotuning=yes for the previously configured tests.
>>
>> Please advise if there’s a bug with this mechanism? It works fine in 3.3.2.
>>
>> Thanks,
>>
>> Roderick
>> --
>> This message is subject to the CSIR's copyright terms and conditions,
>> e-mail legal notice, and implemented Open Document Format (ODF) standard.
>> The full disclaimer details can be found at
>> http://www.csir.co.za/disclaimer.html.
>>
>> This message has been scanned for viruses and dangerous content by
>> MailScanner,
>> and is believed to be clean.
>>
>> Please consider the environment before printing this email.
>>
>
>
> --
> This message is subject to the CSIR's copyright terms and conditions,
> e-mail legal notice, and implemented Open Document Format (ODF) standard.
> The full disclaimer details can be found at
> http://www.csir.co.za/disclaimer.html.
>
> This message has been scanned for viruses and dangerous content by
> MailScanner,
> and is believed to be clean.
>
>
> Please consider the environment before printing this email.
>


--
This message is subject to the CSIR's copyright terms and conditions, e-mail
legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at
http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by
MailScanner,
and is believed to be clean.

Please consider the environment before printing this email.




Archive powered by MHonArc 2.6.16.

Top of Page