Are there methods faster than Strings for sending a sprite's state over UDP?

Question

I'm programming a 2.5D networked game in Java. The networking works like this right now:

1. Create new networked sprite object at the client. Send it to the server. Server distributes and saves it. (TCP-ObjectStreams are used)

2. The Sprite's state is represented by a String that contains its id (Player's name+Index) and values. You can request the state with the method getState():

   return getID()+"|x"+getX()+"y"+getY()+"#";
   //Example: "Grimey2|x402y123#"
   

These states are collected multiple times a second by adding them to a single big String:

zState += spriteArray[x].getState();
//Example: "Grimey1|x752y133#Grimey2|x410y31#Grimey3|x202y13#"

All sprites' states are then saved in a HashMap at the client, sent to the server (Java DatagramSocket) and saved there too.

Is there a more performant way to handle sprite-updating than with Strings?

Answer 1

Assuming the player index is unique, there's no need to send the name along with it each frame. Send the name + index once, store it in a lookup table on the client, and only send the index in your per-frame updates.

Also, if there are multiple location changes per update, why send the ones that have already expired? Unless I'm misunderstanding the purpose, the client only needs to be aware of the most recent state. If it changed 3 times since the last update, and the first two are completely nullified by the third, send only the third (final) state.

As for string vs other format for efficiency, strings are rarely the best choice for anything other than actual text. Establishing a known binary format could further reduce your update token size. For example:

[player_index](2 bytes)[x_position](4 bytes)[y_position](4 bytes)

would allow you to represent the same data in a guaranteed 10 bytes, rather than the variable length strings you're currently using. With a fixed format, you can remove the tokens that appear to be delimiters, "|" and "#" at the beginning and end of the (x.y) data, as well as the 'x' and 'y' labels.

Edit: though you would need to distinguish between player lookup data and player updates, so an additional byte or two at the beginning to identify the format you'll be reading after that would be required.

Answer 2

The source of your performance drain is likely string concatenation. There are great answers here on how to concatenate strings efficiently in Java.

Summary: Learn StringBuilder.

If even this performance boost isn't enough, you could design a binary protocol, but think very, very hard about it first.

Answer 3

Have you looked at how any network libraries are constructed? For java, I would highly recommend the Kryonet Library. It uses a serialization system called Kryo and is very performant with UDP and TCP...

http://code.google.com/p/kryonet/

http://code.google.com/p/kryo/