Yes, you would be surprised at where all the time goes... As Colin said, my advice is to measure everything using something like chrome tools, react's chrome tools or wireshark to find out how long each operation is taking.
If it turns out not to be the network you could be reaching a worst case with react and/or reagent. Maybe your games are too complex for the differencing algorithm and too much is changing each frame or you aren't using key= properly. One copy may work fine but maybe it doesn't scale. The react chrome tools should help you figure out what is going on. Surprisingly, iframes can come in handy but less so as a UI feature and more as a performance tool. We have a page that has to display a small window of uncompressed video from a web socket onto a canvas element at 16-24 frames/sec and doing this in the main page/thread sucked up so much cpu that other background processing on the page was delayed or blocked and we were forced to move it to its own iframe. Most browsers give each page at least one thread, including iframes. YMMV. Good luck. Alan -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
