ePMP 3000 Frame Size

If we're trying to sync an ePMP 3000 with other ePMP 1000/2000 APs, am I correct that the Frame Size setting on the 1000/2000 should be at 2.5ms?

Today ePMP3000 supports only 5 ms Frame Size.
So 5 ms should be configured at ePMP1000/2000 as well.

Thank you.

Thank you.

Is 2.5ms planned for a future update?

We have plans to introduce 2.5ms soon.

Thank you.

Any update or ETA on 2.5ms frame size?

2 Likes

@dkeltgen wrote:

Any update or ETA on 2.5ms frame size?


We are currently testing 2.5 ms frame.

It will be introduced in the 4.5 Beta FW in few weeks.

Thank you.

News?

I see important improvment on TCP throughput using 2.5ms.

But I loose force300 on epmp2000 AP


@Mirko wrote:

News?

I see important improvment on TCP throughput using 2.5ms.

But I loose force300 on epmp2000 AP


So FYI... setting to 5ms increases throughput over 2.5ms frames, by around 10%. If you want slightly lower latency (shaves 5-10ms off) and the ability to sync with PMP450 radios that also use 2.5ms timing, then use that.

FWIW we switched over our entire network to 5ms frames recently and haven't looked back. Zero users have complained about latency issues and all our AP's get a throughput boost.

So, as usual, I agree with Eric.  We have places where the 5.0 ms frames gives a boost in performance and stability, and in those places, that's more beneficial than a few ms lower latency.

Especially when you consider end-to-end latency.  If you JUST look at the SM-to-AP, latency changing from 8 ms to 15 ms, that seems like a big jump .  But if you ping all the way to the server - such as pinging 'google,com' or 'steamgames.com', then the SM-to-Server ping times difference might be more like 58 ms with 2.5ms fames, changing to 65 ms with 5.0ms frames, which then is a very small percentage change.


@Mirko wrote:

News?   ...using 2.5ms. But I loose force300 on epmp2000 AP


So, if you do want to try Force300's with 2.5ms frames, you can take this for what it's worth... in the PTP550 Beta Forum, there is an early beta of 4.5 for the PTP550.  The PTP550 does use the same AC Wave2 Chipset as the Force300's, so you may want to try this 4.5RC-28 Beta Software on a Force300, and see what it does as far as connecting with your 2.5ms AP.  :)

http://community.cambiumnetworks.com/t5/PTP-Beta/Beta-Release-4-5RC-28-now-available-for-trials-DCS-and-ACS/m-p/111182#M97

Of course - understand that is an early, non-released, beta, so your mileage may vary. I would recommend you try it in your shop first (and not out in the wild), and see what results you get. :)  It may instigate P'on Farr and drive your Force300 insane..

I tried framesize 2.5 and 5.0

I see better TCP results in 2,5 instead of 5,0

but if you only test using "Cambium Wireless Test", that is UDP, you see higher number, but in real life UDP is not the most used protocol.

So I prefer see lower number in UDP test but greater numbers in TCP real application.

Today I need to set all on 5,0ms for 300 series compatibility, but I loose performance

Hi. Did you try the PTP550 beta 4.5 software on a Force300 to see how that works on your 2.5ms AP?