It's cool to hear that your project seems to be coming along well. Some things that I can think of that might help:

Have you tried GZipping/compressing the data before sending it through the web socket?

Maybe consider messing with these values <https://github.com/NetLogo/Galapagos/blob/423ba321dfd2382f6ec9ff76ee45aeb77c013b42/app/assets/javascripts/TortoiseJS/control/session-lite.coffee#L1-L9> to slow down the redraw rate?

Another thing you might consider is actually not having the clients render the updates at all. Instead, you might use less bandwidth if you simply have the server render the updates and then send each of the clients an image to display in the View. That's how one of our old prototypes for NetLogo Web worked. The performance was actually not awful.

On 07/28/2015 05:56 PM, Oscar Martinez wrote:
Hi,

I've been working on a project where I take one of the standalone models generated by Galapagos and after that I add some custom code for connecting and synchronizing two (or more) different instances of that model, using NodeJS and WebSockets.

For updating the changes on the model, I overwrite the method < AgentStreamController.prototype.applyUpdate(modelUpdate) >. The thing is, that I send through WebSockets all the modelUpdate object, that it's big. So, I would like to know if you have any other idea about how to do it sending (and receiving) less data between client-server-client.

Thanks,
--
You received this message because you are subscribed to the Google Groups "netlogo-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to netlogo-devel+unsubscr...@googlegroups.com <mailto:netlogo-devel+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups 
"netlogo-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to netlogo-devel+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to