[Nfd-dev] How to see data retrieve / download time using "ndngetfile" command?
Md Toufiqul Islam
toufiqulislam.bd at gmail.com
Thu Jan 12 04:52:30 PST 2017
Dear Mr. Klaus,
I would like to thank you from deep of my heart for your help & guideline.
Things are working perfectly now, exactly what I am looking for. It was my
fault to use a very small txt file for testing purpose.
I wish you all the best. Be well & take care.
Best regards
Muhammad
On Thu, Jan 12, 2017 at 1:06 PM, Md Toufiqul Islam <
toufiqulislam.bd at gmail.com> wrote:
> Hi Klaus,
>
> Thanks for your guideline. I have done exactly how you have explained. But
> still no sign of showing the "Time used". Am I doing anything wrong?
>
> *# ndnputchunks -p -v /abc < /home/remoteserver/Downloads/rony.txt*
>
> Loading input ...
> Created 1 chunks for prefix /abc
> %FD%00%00%01Y%92%7F%7F%60
> Data published with name: /abc/%FD%00%00%01Y%92%7F%7F%60
>
>
> *# ndncatchunks -v -t aimd -S /abc*
>
> RttEstimator initial parameters:
> Alpha = 0.125
> Beta = 0.25
> K = 4
> Initial RTO = 1000 milliseconds
> Min RTO = 200 milliseconds
> Max RTO = 4000 milliseconds
> Pipeline basic parameters:
> Max retries on timeout or Nack = 3
> Interest life time = 4000 milliseconds
> Allow stale content
> Verbose output enabled
> Print summary to std err enabled
> PipelineInterestsAimd initial parameters:
> Initial congestion window size = 1
> Initial slow start threshold = 2.14748e+09
> Multiplicative decrease factor = 0.5
> Additive increase step = 1
> RTO check interval = 10 milliseconds
> Max retries on timeout or Nack = 3
> Conservative Window Adaptation enabled
> Resetting cwnd to ssthresh when loss event occurs
> Data: Name: /abc/%FD%00%00%01Y%92%7F%7F%60/%00%00
> MetaInfo: ContentType: 0, FreshnessPeriod: 10000 milliseconds,
> FinalBlockId: %00%00
> Content: (size: 13)
> Signature: (type: 1, value_length: 256)
>
> Discovered version = 1484221546336
> Timeout for Interest /abc?ndn.MinSuffixComponents=
> 3&ndn.MaxSuffixComponents=3&ndn.ChildSelector=1&ndn.Nonce=
> 573151652&ndn.Exclude=*,%FD%00%00%01Y%92%7F%7F%60
> Timeout for Interest /abc?ndn.MinSuffixComponents=
> 3&ndn.MaxSuffixComponents=3&ndn.ChildSelector=1&ndn.Nonce=
> 2787869428&ndn.Exclude=*,%FD%00%00%01Y%92%7F%7F%60
> Found data with the latest version: 1484221546336
> Hi i am rony
>
>
>
>
> *# ndncatchunks -v -t fixed -S /abc*Data: Name:
> /abc/%FD%00%00%01Y%92%7F%7F%60/%00%00
> MetaInfo: ContentType: 0, FreshnessPeriod: 10000 milliseconds,
> FinalBlockId: %00%00
> Content: (size: 13)
> Signature: (type: 1, value_length: 256)
>
> Discovered version = 1484221546336
> Timeout for Interest /abc?ndn.MinSuffixComponents=
> 3&ndn.MaxSuffixComponents=3&ndn.ChildSelector=1&ndn.Nonce=
> 3287183225&ndn.Exclude=*,%FD%00%00%01Y%92%7F%7F%60
> Timeout for Interest /abc?ndn.MinSuffixComponents=
> 3&ndn.MaxSuffixComponents=3&ndn.ChildSelector=1&ndn.Nonce=
> 252627901&ndn.Exclude=*,%FD%00%00%01Y%92%7F%7F%60
> Found data with the latest version: 1484221546336
> Hi i am rony
>
>
>
> Best regards
> Muhammad
>
> On Thu, Jan 12, 2017 at 5:38 AM, Klaus Schneider <klaus at cs.arizona.edu>
> wrote:
>
>> You can get all the files with:
>>
>> # git clone https://gerrit.named-data.net/ndn-tools
>> # cd ndn-tools/
>> # git fetch https://gerrit.named-data.net/ndn-tools
>> refs/changes/32/3432/4 && git checkout FETCH_HEAD
>>
>> Then look in the folder "ndn-tools/tools/chunks/catchunks"
>>
>> Moreover, you can find them on gerrit. For example:
>> https://gerrit.named-data.net/#/c/3432/4/tools/chunks/catchu
>> nks/pipeline-interests-fixed-window.cpp
>>
>> Best regards,
>> Klaus
>>
>> On 01/11/2017 07:04 PM, Md Toufiqul Islam wrote:
>>
>>> Dear Klaus,
>>>
>>> Thank you once again for your great help. This is exactly what I need.
>>> But as I have very bad programming experience, I couldn't able to
>>> configure it properly. Is is possible or permissible to ask you for the
>>> modified cpp & hpp file so that I can just replace with my old files?
>>>
>>> regards
>>> Muhammad
>>>
>>> On Wed, Jan 11, 2017 at 11:20 PM, Niv Sardi <xaiki at endlessm.com
>>> <mailto:xaiki at endlessm.com>> wrote:
>>>
>>> Hello,
>>> you can check out our chunks implementation (a little different from
>>> the NDN cat/put chunks one) that implements a GObject layer for
>>> progress/complete signal if that's usefull for you:
>>> https://github.com/endlessm/endless-ndn/blob/master/eos_data
>>> _distribution/ndn/chunks.py
>>> <https://github.com/endlessm/endless-ndn/blob/master/eos_dat
>>> a_distribution/ndn/chunks.py>
>>>
>>> On Wed, Jan 11, 2017 at 6:14 PM, Klaus Schneider
>>> <klaus at cs.arizona.edu <mailto:klaus at cs.arizona.edu>> wrote:
>>>
>>> We are currently updating the ndncatchunks code:
>>> https://gerrit.named-data.net/#/c/3432/
>>> <https://gerrit.named-data.net/#/c/3432/>
>>>
>>> you can check the code out via "git fetch
>>> https://gerrit.named-data.net/ndn-tools
>>> <https://gerrit.named-data.net/ndn-tools> refs/changes/32/3432/4
>>> && git checkout FETCH_HEAD"
>>>
>>> It contains a function printSummary() which might be what you
>>> want:
>>>
>>> void
>>> PipelineInterestsFixedWindow::printSummary() const
>>> {
>>> time::steady_clock::duration dur =
>>> time::steady_clock::now() - m_startTime;
>>> double timePassed = static_cast<double>(dur.count()) /
>>> 1000000; // in ms
>>> double throughput = (8 * m_receivedSize * 1000) /
>>> timePassed;
>>> std::string throughputUnit;
>>>
>>> computeThroughput(throughput, throughputUnit);
>>>
>>> std::cerr << "\nAll segments have been received.\n"
>>> << "Total # of segments received: " <<
>>> m_nReceived << "\n"
>>> << "Time used: " << timePassed << " ms" << "\n"
>>> << "Goodput: " << throughput << " " <<
>>> throughputUnit << "\n";
>>> }
>>>
>>>
>>> Best regards,
>>> Klaus
>>>
>>> On 01/11/2017 01:49 PM, Md Toufiqul Islam wrote:
>>>
>>> Dear Klaus,
>>>
>>> Thank you so much for your reply. File transfer / retrieval
>>> is not the
>>> problem. Problem is retrieval time (millisecond).
>>>
>>> I have already tried ndncatchunks / ndnputchunks. But these
>>> doesn't
>>> provide me any information about download time / retrieval
>>> time of the
>>> contents either. Is there any other idea ?
>>>
>>>
>>> Best regards
>>> Muhammad
>>>
>>>
>>> On Wed, Jan 11, 2017 at 7:17 PM, Klaus Schneider
>>> <klaus at cs.arizona.edu <mailto:klaus at cs.arizona.edu>
>>> <mailto:klaus at cs.arizona.edu <mailto:klaus at cs.arizona.edu>>>
>>>
>>> wrote:
>>>
>>> Hi Muhammad,
>>>
>>> you might want to use ndncatchunks/ndnputchunks from
>>> https://github.com/named-data/ndn-tools
>>> <https://github.com/named-data/ndn-tools>
>>> <https://github.com/named-data/ndn-tools
>>> <https://github.com/named-data/ndn-tools>>
>>>
>>> Best regards,
>>> Klaus
>>>
>>>
>>> On 01/11/2017 10:49 AM, Md Toufiqul Islam wrote:
>>>
>>> Hello Everyone,
>>>
>>> I hope all of you are doing great. I have a very
>>> small question
>>> which I
>>> couldn't find any solution yet. I believe this is
>>> the right
>>> place to ask
>>> about.
>>>
>>> I have installed nfd, ndn-cxx and Repo-ng on two of
>>> computers
>>> willing to
>>> insert & retrieve data to & from data repository. I
>>> have done this
>>> successfully using ndnputfile & ndngetfile command.
>>> But after
>>> retrieving any data using "ndngetfile" command, it
>>> doesn't show
>>> me any
>>> message regarding how much time it needed to fetch
>>> the required data
>>> from the repository. Can anyone help me regarding
>>> that? How can
>>> I see
>>> the download time?
>>>
>>> Here is an example. When I retrieve a file from one
>>> computer to
>>> other,
>>> ndngetfile shows the following message:
>>>
>>> ndngetfile /example/data/1/test.txt
>>>
>>>
>>> INFO: End of file is reached.
>>> INFO: Total # of segments received: 188
>>> INFO: Total # bytes of content received: 187537
>>>
>>> On the above, there are no information about
>>> retrieve/download
>>> time of
>>> the received data. How can I see retrieve/download
>>> time? I will
>>> be glad
>>> to have valuable reply from yours.
>>>
>>> With regards
>>> Muhammad Toufiqul
>>>
>>>
>>> _______________________________________________
>>> Nfd-dev mailing list
>>> Nfd-dev at lists.cs.ucla.edu
>>> <mailto:Nfd-dev at lists.cs.ucla.edu>
>>> <mailto:Nfd-dev at lists.cs.ucla.edu
>>> <mailto:Nfd-dev at lists.cs.ucla.edu>>
>>>
>>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>>> <http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev>
>>>
>>> <http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>>> <http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev>>
>>>
>>>
>>> _______________________________________________
>>> Nfd-dev mailing list
>>> Nfd-dev at lists.cs.ucla.edu <mailto:Nfd-dev at lists.cs.ucla.edu>
>>> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev
>>> <http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev>
>>>
>>>
>>>
>>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20170112/804e2cf6/attachment-0001.html>
More information about the Nfd-dev
mailing list