These are chat archives for fanout/pushpin

8th
Aug 2018
Justin Karneges
@jkarneges
Aug 08 2018 01:28
tcpkali. good for creating lots of connections efficiently. also if it receives a specially-formatted timestamp from the server, it will compare it to the current time to determine latency, which is nice
Justin Karneges
@jkarneges
Aug 08 2018 01:35
@yehosef_gitlab mainly when there's activity, especially sending to multiple clients at once. pushpin can send around 5k messages/sec. as you get into the tens of thousands of connections, broadcasts will get slower and hog cpu
so this is why we recommend max 10k concurrent. it's certainly not a hard number. message rate may be a more important number depending on use case
Justin Karneges
@jkarneges
Aug 08 2018 01:41
but in general we've never found memory to be an issue and I think most users would hit cpu problems first as their load grows
Sumit Chahal
@smtchahal
Aug 08 2018 02:32
Hi everyone,
I'm sorry if this is covered somewhere in the docs and I missed it, but is it possible to publish to multiple channels in one request to Pushkin's private server (that
Runs on port 5561)?
Sumit Chahal
@smtchahal
Aug 08 2018 02:38
Pushpin*
Sumit Chahal
@smtchahal
Aug 08 2018 04:14
Okay, so apparently all I have to do is pass multiple "items" in the JSON data I POST to Pushpin's control API, right? Each with the same message (if that's what I want)?
Justin Karneges
@jkarneges
Aug 08 2018 15:21
@smtchahal yes
Adrian
@picarsite
Aug 08 2018 20:24
Hi, how do you guys create a unit test? Pushpin is necessary to be able to sent requests to the server app.
Adrian
@picarsite
Aug 08 2018 20:36
(websocket)
Adrian
@picarsite
Aug 08 2018 20:43
Sending simple requests is not possible because there is no WebSocketContext: const ws = expressGrip.getWsContext(res); .... ws becomes "null".