poor performance

[peterrz]

unfortunately, testing shows that Odin has poor performance especially: in deliver packets and delay (most of the packets will get lost). earlier I had problems with the ping then I figure it out, I should add some flow manually, but now I need your guidance to solve these problems: first of all, I'm using some code to access The Queue which was defined by you to manage transform packets. as you see in below there are some packets in and out but queue length remained empty (code to access the queue is correct). why the Queue remained empty and how it will be filled up?

Another question related to performance. I used the Iperf to fill up the queue and increase the traffic loads on the access point. the result is shown in the below that we have only first packets in and out. how can we stable the link? and why just we have a send and receive data per each test? (i used many devices, scenarios and different Iperf version but the results were same)

thanks!

[josemariasaldana]

Odin Wi-5 is just a proof-of-concept. We are running some validations, but there are some things that may not work as in a commercial device.

This said, it seems that there is some problem in your setup. In our tests, we get much more throughput. Please check each part carefully. https://github.com/Wi5/odin-wi5/wiki/Sanity-check

[Viomnice]

Hello, peterrz: I am very interesting in accessing the Queue length real-time, and I already sent an email to your gmail. I hope you can tell me how to implement this function in odinagent.cc. thanks!

[peterrz]

@Viomnice dear, did you get the mail? how is going?

[Viomnice]

@peterrz Hello, I can only get the length of the queue in the downlink (from ap to sta), but I also want to get the length of the queue in the uplink (from sta to ap) by adding the SimpleQueue component instead of using FromDevice(.., HEADROOM queuelength), and i tried to add the SimpleQueue to the existing configuration file but always fail to succeed. Do you have any good ieads for this? Thanks!

[Viomnice]

@peterrz The main reason for the failure is that the downlink in the existing configuration file is composed of toHost(ap) instead of toDevice.

[peterrz]

@Viomnice hello dear, would you please send me your script? (agent.cli) why don't you use the counter instead of the SimpleQueue? did you use the clicky?

[peterrz]

@Viomnice

@peterrz The main reason for the failure is that the downlink in the existing configuration file is composed of toHost(ap) instead of toDevice.

unfortunately, it doesn't work cause toDevice(ap) is an unknown device for the router. did you find out how to use it?

[sayed-amir]

@peterrz Hello Pourya. I am wondering if you found the issue that caused the poor performance. Would you please share your experience?

I have packet loss and can see MAC layer CRC mismatch for some packets in Wireshark .

[peterrz]

@hoseiniamir Hello Hoseini. Unfortunately, I couldn't find a better solution, so I held on to this:

josemariasaldana commented on Mar 13, 2018 "Odin Wi-5 is just a proof-of-concept"

But I will be happily sharing my experience with you