Thanks Etienne, no worries, just tell me your username and I can grant you permissions. What’s your wiki username?
Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Chief Architect Instrument Software and Science Data Systems Section (398) NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 168-519, Mailstop: 168-527 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Associate Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Etienne Koen <[email protected]> Date: Wednesday, November 12, 2014 at 4:08 PM To: Chris Mattmann <[email protected]>, Shakeh Khudikyan <[email protected]> Cc: Chris Mattmann <[email protected]>, "[email protected]" <[email protected]> Subject: RE: OODT buffer size >Thanks Chris, > >It does not seem like I have permissions to create a page for the >results. I can't get any link on the page you sent which gives me that >option. I am logged in... > >Sorry, maybe I am missing something obvious... > >Cheers > >Etienne Koen > >Data Processing Systems Engineer > >Space Advisory Company > >O: +27 (21) 300 0060 I C: +27 (76) 661 0170 I E: [email protected] > >________________________________________ >From: Mattmann, Chris A (3980) [[email protected]] >Sent: Wednesday, November 12, 2014 4:12 PM >To: Etienne Koen; Khudikyan, Shakeh E (398M) >Cc: [email protected]; [email protected] >Subject: Re: OODT buffer size > >Thank you Etienne, this is great. I would appreciate you putting up a >wiki page at: > >https://cwiki.apache.org/confluence/display/OODT/Home > > >That captures this information and helps folks to collaborate if you >have time. If you need permissions on the wiki space just register for >CWIKI at Apache and tell me your username I¹ll grant you permissions. > >As to having a config file in OODT PushPull to set the buffer size, >there isn¹t one (it relies on whatever the underlying operating >system uses - so like you found out if you are on Linux flavors, the >solution you present below is a good way to set this). > >HTH! > >Cheers, >Chris > >++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >Chris Mattmann, Ph.D. >Chief Architect >Instrument Software and Science Data Systems Section (398) >NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >Office: 168-519, Mailstop: 168-527 >Email: [email protected] >WWW: http://sunset.usc.edu/~mattmann/ >++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >Adjunct Associate Professor, Computer Science Department >University of Southern California, Los Angeles, CA 90089 USA >++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > > >-----Original Message----- >From: Etienne Koen <[email protected]> >Date: Wednesday, November 12, 2014 at 8:51 AM >To: Shakeh Khudikyan <[email protected]> >Cc: Chris Mattmann <[email protected]> >Subject: OODT buffer size > >>Hi Shakeh, >> >>Hope all is well! >> >>I am still busy with evaluating OODT... Currently I am exploring the tool >>using different TCP transfer window sizes. I done this by editing >>/etc/sysctl.conf and setting the variables >> >>net.core.rmem_default >>net.core.rmem_max >>net.core.wmem_default >>net.core.wmem_max >> >>I have attached the results I found for varying the transfer window on >>both the client and server. >> >>However, I was unable to found an OODT configuration file to set the >>buffer size. Is there such file where I can do this? >> >>Thanks! >> >>Etienne Koen >> >>Data Processing Systems Engineer >> >>Space Advisory Company >> >>O: +27 (21) 300 0060 I C: +27 (76) 661 0170 I E: [email protected] >> >>________________________________ >> >>Disclaimer: This E-mail message, including any attachments, is intended >>only for the person or entity to which it is addressed, and may contain >>confidential information. Each page attached hereto must also be read in >>conjunction with this disclaimer. >>If you are not the intended recipient you are hereby notified that any >>disclosure, copying, distribution or reliance upon the contents of this >>e-mail is strictly prohibited. E.&O.E. > > >________________________________ > >Disclaimer: This E-mail message, including any attachments, is intended >only for the person or entity to which it is addressed, and may contain >confidential information. Each page attached hereto must also be read in >conjunction with this disclaimer. >If you are not the intended recipient you are hereby notified that any >disclosure, copying, distribution or reliance upon the contents of this >e-mail is strictly prohibited. E.&O.E. > >________________________________ > >Disclaimer: This E-mail message, including any attachments, is intended >only for the person or entity to which it is addressed, and may contain >confidential information. Each page attached hereto must also be read in >conjunction with this disclaimer. >If you are not the intended recipient you are hereby notified that any >disclosure, copying, distribution or reliance upon the contents of this >e-mail is strictly prohibited. E.&O.E.
