[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cf-dev] Problem while using Netem for benchmarking large-large post in Californium
|
Hi,
We are using the large-large post scenario
available in plugtestClient and pugtestServer in the master branch of californium
without any changes (other than closing all other tests).
Regards
Abhijan Bhattacharyya
Associate Consultant
Scientist, Innovation Lab, Kolkata, India
Tata Consultancy Services
Mailto: abhijan.bhattacharyya@xxxxxxx
Website: http://www.tcs.com
____________________________________________
Experience certainty. IT Services
Business Solutions
Consulting
____________________________________________
From:
"Hudalla Kai (INST/ESY1)"
<Kai.Hudalla@xxxxxxxxxxxx>
To:
"cf-dev@xxxxxxxxxxx"
<cf-dev@xxxxxxxxxxx>
Date:
10/20/2016 04:57 PM
Subject:
Re: [cf-dev]
Problem while using Netem for benchmarking large-large post in Californium
Sent by:
cf-dev-bounces@xxxxxxxxxxx
Mabye you can still share the answer to my question(s):
What version of Californium are you using?
Can you share the code you are using for your test case? On client and
server
side (i.e. the Resource you have registered in CoapServer?
--
Mit freundlichen Grüßen / Best regards
Kai Hudalla
Chief Software Architect
Bosch Software Innovations GmbH
Schöneberger Ufer 89-91
10785 Berlin
GERMANY
www.bosch-si.com
Registered office: Berlin, Register court: Amtsgericht Charlottenburg,
HRB 148411 B;
Executives: Dr.-Ing. Rainer Kallenbach, Michael Hahn
On Do, 2016-10-20 at 14:55 +0530, Abhijan Bhattacharyya wrote:
> Hi,
> Thanks a lot for your response. We are trying to bench-mark a typical
large-
> large post scenario (the payload type does not matter much; simple
ASCII texts
> will do) under different network bandwidth and loss situation. We
are doing
> this as a background study which would help in choosing the right
candidate to
> build some solutions in future which would require such large POSTs.
> However, whenever we put the loss in the system using 'Netem' or 'iptables'
we
> see the odd behaviour. At times the client code crashes as the POST
handler,
> rather than going to the time-out-and-retransmit loop in case of an
emulated
> loss, gets a NULL response.
> Interestingly, since yesterday we started experimenting the same scenario
using
> CoAPthon (the python implementation of CoAP). In this case the code
does not
> crash, but occasionally stalls indefinitely if there is a loss of
control
> traffic.
> Really no idea what is going on. With emulated loss the system is
becoming
> really unpredictable. At times the exchange (about 4 blocks with 1024
bytes
> each) successfully happens with several retransmits of the blocks.
But at times
> it stalls after exchanging one or two blocks.
>
> We have created an isolated network with two machines connected over
a 3rd
> router (with 2 interfaces). The loss is incorporated in the 3rd one.
We have
> also experimented with back to back connected client-server where
the loss is
> applied at the server NIC.
>
>
> Regards
> Abhijan Bhattacharyya
> Associate Consultant
> Scientist, Innovation Lab, Kolkata, India
> Tata Consultancy Services
> Mailto: abhijan.bhattacharyya@xxxxxxx
> Website: http://www.tcs.com
> ____________________________________________
> Experience certainty. IT Services
>
Business Solutions
>
Consulting
> ____________________________________________
>
>
>
>
> From: "Hudalla Kai (INST/ESY1)"
<Kai.Hudalla@xxxxxxxxxxxx>
> To: "cf-dev@xxxxxxxxxxx" <cf-dev@xxxxxxxxxxx>
> Date: 10/20/2016 01:18 PM
> Subject: Re: [cf-dev] Problem while using
Netem for benchmarking large-
> large post in Californium
> Sent by: cf-dev-bounces@xxxxxxxxxxx
>
>
>
> Hi Abhijan,
>
> I have to admit that the blockwise support in Californium is not the
best
> maintained and understood area of functionality. We have even been
thinking
> about
> re-factoring support for "transparent" blockwise transfers
out of Californium's
> core stack and maybe into the CoapClient component only. However,
I am still
> interested in your test case, so it would be helpful to know what
you are
> actually trying to do and, most importantly, what version of Californium
you
> are
> using. If you think that what you experience is a bug, then you might
also
> consider creating an issue on GitHub [1].
>
> [1] https.//github.com/eclipse/californium
>
> _______________________________________________
> cf-dev mailing list
> cf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cf-dev
_______________________________________________
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-dev
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you
