[ENet-discuss] Large data packets over ENet

[Tim Auld]

Firstly, if you follow convention, the process that displays the rendered images is called the client, and the other processes are the servers.  This is because the client asks a server to do some work for it, no matter the relative number of processes.  Really, your client (the renderer with work it needs done) should connect to multiple servers... not the other way around.

Question: do you really mean 650 kilobits per frame, or do you mean kilobytes?  512*384*4 = 768KB.  While it's not impossible to compress that to 650Kb (about 83KB), using something like JPEG, it would probably take quite a lot of time to do that compression.  There's a big difference.  After doing some calculation, I think you could only achieve about 20fps on a 100Mbps ethernet with 650KB frames.

Tim

  ----- Original Message ----- 
  From: Jacco Bikker 
  To: enet-discuss at cubik.org 
  Sent: Wednesday, February 02, 2005 2:44 AM
  Subject: [ENet-discuss] Large data packets over ENet


  Hello,

   

  I am writing a ray tracer that renders at interactive frame rates on a single machine (2Ghz, 5fps). To advance to realtime performance, I am trying to use several computers to render the image. I tried using winsock/UDP, but I lack the knowledge to properly implement this, and the result was disappointing for anything above 2 clients.

   

  So I tried Enet. Implementation was a breeze, but performance is somewhat disappointing. Perhaps I am doing something wrong, so let me explain what I do:

  -          The server accepts incoming clients.

  -          Once at least one client is available, the server sends a 'go' packet to each client. This packet contains information about which lines the client should render.

  -          The client receives this information, starts rendering, and returns the result to the server.

   

  The maximum amount of returned pixel data is 512x384 pixels (32bit). This is about 650Kb per frame. Using Enet, performance is significantly better (but still disappointing) if I compress the data. Does Enet have problems with large data streams? Is there a way to optimize this?

   

  - Jacco.



------------------------------------------------------------------------------


  _______________________________________________
  ENet-discuss mailing list
  ENet-discuss at cubik.org
  http://lists.cubik.org/mailman/listinfo/enet-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.puremagic.com/pipermail/enet-discuss/attachments/20050202/5aecb026/attachment.html