objective c - iPhone: Which are the most useful techniques for faster Bluetooth? -


I am adding peer-to-peer bluetooth using the gamekit in the iPhone shoot-m-up, so speed is important is. I am sending about 40 messages in a different way each other, most of which are fastest GKSendDataUnreliable, all serial with NSCoding. In testing between 3G and 3GS, this is slowing down 3G as much as I want. I am thinking that I should focus on efforts to speed it up.

How slow is GS & DData? To get there is for some packets, it may be faster to send a GKSandDetDableable and send a receipt to Peer so that I can send it again if I do not get inside the house, say Are 100 ms?

Rather than collecting the NSCoding protocol, how fast would it be to create an NSData instance using a regular C array? Is this a serialization process (for about a dozen floats) as slow as slow is it as if you expect the object creation / deolocation overhead, or something is particularly slowing down?

I have heard that (for example) different sets of data are too much, very slow, by sending a figure four times the size. Can I make a significant saving by sending different packets of data that are not always together in the same packet?

Is there any other Bluetooth display secret that I've missed?

Thank you for your help.

I'm not a bluetooth expert, but normally sending reliable data using 1.5x The speed of sending data is incredible. I would like to avoid trying to send an ACK back by using an incredible method, because then you will know whether the ACK has failed to reach or not, you need to put all the ridiculous arguments that send you reliable messages. Instead of doing very slow.

There is more latency in sending data which means that sending 4 small packets will take longer than sending 1 packet with 4 pixels payload. At any time you can increase the payload size to minimize, you will get an execution benefit.

If you know the size and size of sending and receiving data, then you can also squeeze some performance by sending arrays of byte arrays or numbers instead of using NSCoding, because by NSCID It's going to use some time to serialize and de-serialize (if you are only sending the arrays, you can skip one step) and the amount of data you send will be a little bit from NSCoder It will be a raw array with more.


Comments

Popular posts from this blog

windows - Heroku throws SQLITE3 Read only exception -

lex - Building a lexical Analyzer in Java -

python - rename keys in a dictionary -