public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Mickael Chazaux <mickael.chazaux@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Performance considerations
Date: Thu, 26 Feb 2009 12:59:45 +0100	[thread overview]
Message-ID: <bc36f8ed0902260359t6a3fe2c0vc4baefd3c205cebf@mail.gmail.com> (raw)

Hello,

I am programming with bluez in C, transfering data from a linux PC to a
java application on a phone. All works fine. I have some performance
questions.

When I use L2CAP sockets, I get an average of 10% better bitrate on a
given pair PC/phone than with RFCOMM sockets. Also, changing the MTU
of the L2CAP socket has an impact on bitrate. An MTU of 672 on some
phones gives a average bitrate of 190kB/s, nearly 50% more than with
an MTU of 256 bytes.

Also, in noisy environements (with lots and lots of phones with
bluetooth enabled), there is a great decrease in performance (
an average of 50kB/s with a good phone).

What bitrate values can you achieve? Can I expect an amelioration, for
example on fine tuning the stack's parameters, to get the maximum
bitrate possible?

Regards,
Mickael

                 reply	other threads:[~2009-02-26 11:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bc36f8ed0902260359t6a3fe2c0vc4baefd3c205cebf@mail.gmail.com \
    --to=mickael.chazaux@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox