Not an Om user here but sounds like you are receiving messages faster than you can handle them.
A "slow consumer" is a common problem in a messaging situation and core.async has 2 built-in ways to deal with that. You can either use (async/chan (async/slliding-buffer n)) or (async/dropping-buffer n), both will start dropping messages either at the head or tail of the buffer. Contrary to popular believe React is actually quite slow when doing alot of state updates, it just doesn't appear that way since all updates are batched together in a "frame". If you can't afford to drop messages you could try using a WebWorker to do processing in another thread and push state updates seperately. But, as I said, not an Om user, just an educated guess. Cheers, /thomas -- 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 clojurescript+unsubscr...@googlegroups.com. To post to this group, send email to clojurescript@googlegroups.com. Visit this group at http://groups.google.com/group/clojurescript.
