Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gatt_notify too slow on Broadcast #33261

Closed
CodingGhost opened this issue Mar 11, 2021 · 3 comments
Closed

gatt_notify too slow on Broadcast #33261

CodingGhost opened this issue Mar 11, 2021 · 3 comments
Assignees
Labels
area: Bluetooth bug The issue is a bug, or the PR is fixing a bug

Comments

@CodingGhost
Copy link
Contributor

I am using ble_gatt_notify to push data to all connected clients, but it is way to slow if multiple devices are connected.
I am passing NULL as connection pointer.

To Reproduce
try to get High throughput (MTU > 260) to multiple clients using bt_gatt_notify

Expected behavior
it would be expected, that the speed is halfed with 2 devices, but its more like 10% of what it is with just one device

Impact
cannot roll out feature

Environment (please complete the following information):

  • Toolchain PlatformIO with ARMGCC
  • V2.5.0
@CodingGhost CodingGhost added the bug The issue is a bug, or the PR is fixing a bug label Mar 11, 2021
@cvinayak
Copy link
Contributor

@CodingGhost Please provide details of reproducing the issue like a simple application or modified zephyr sample that I can use for analysis. Tx buffer count are shared across connections, based on how many connections and number of available Tx buffers your throughput will be affected.

@CodingGhost
Copy link
Contributor Author

CodingGhost commented Mar 12, 2021

I will try to boil down my app to a demo, but It will take some time.

@CodingGhost
Copy link
Contributor Author

ok, I kinda sorted it out. a buffer in my code was too small, and because of that the effective packetsize was way too small. Now I have the throughput that I wanted. I dont think it had something todo with Zephyr anymore.

Sorry for the inconvenience caused!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Bluetooth bug The issue is a bug, or the PR is fixing a bug
Projects
None yet
Development

No branches or pull requests

4 participants