Replacing core.async about sente

[ptaoussanis]

Hey Michael,

I'm investigating Sente but don't want to use core.async (it is not particularly efficient for my workload). Instead, I'd like to use or integrate Meltdown.

Sure - I'll be able to advise better if you could give a little more detail on what you mean by "not particularly efficient for your workload"?

Note that in tests I've run, the network times dominate all others by several orders of magnitude. After that there's the Clojure reader time. Other aspects (incl. core.async) barely register as a rounding error.

I'm not familiar with Meltdown - does it have ClojureScript support?

Note that nothing would stop you from treating core.async as a lib implementation detail server-side and just dumping channel contents into your own stream processing system (I do this myself, but not for performance reasons). This'd be perfectly idiomatic if you wanted Meltdown's API, for example.

Does that help at all? Otherwise pop me some more details and let's go from there :-)

Cheers!

[michaelklishin]

I need an in-process message passing library and Reactor is an order of magnitude more efficient than core.async with a fairly small number of channels (say, dozens). Then I need last mile delivery to WebSocket clients. I have other reasons to use Reactor and Meltdown, too.

So, I primarily need to push data to clients (98% of traffic).

[ptaoussanis]

Reactor is an order of magnitude more efficient than core.async

That may be, but in this context it's analogous to being concerned with how long it takes to answer the doorbell when the postman rings for a package that's been sent by ship from Tanzania :-)

I have other reasons to use Reactor and Meltdown, too.

Sure, that wouldn't be a problem. Server-side I'd just dump content from the channel to your usual pipeline. Like I say, I do this myself - it's perfectly idiomatic.

Note that core.async is being used as an implementation detail behind-the-scenes (notably client-side), so it'd be a dependency either way - but you can basically ignore it server-side once events are delivered.

Does that help? Meltdown looks cool btw :-)

[michaelklishin]

It's fine to have core.async on the client — Meltdown cannot be used from ClojureScript — but I don't need it on the server, which is what my question was about.

[ptaoussanis]

Sure. Okay, so closing - feel free to reopen if you have any follow-up questions later.