HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
chrismccord
channelsac
Ruby2016–2016
chrismccord / channelsac

channelsac

Discover this repository through its Hacker News conversations.

2Distinct people
2Mentions
0Explicit recommenders
31GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2016-08-11 08:56:20 UTC to 2016-08-11 14:59:39 UTC.

012016-08-11 08:00:00 UTC to 2016-08-11 09:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 11, 08:002016-08-11 09:00:00 UTC to 2016-08-11 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-08-11 10:00:00 UTC to 2016-08-11 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-08-11 11:00:00 UTC to 2016-08-11 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 11, 11:002016-08-11 12:00:00 UTC to 2016-08-11 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-08-11 13:00:00 UTC to 2016-08-11 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-08-11 14:00:00 UTC to 2016-08-11 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 11, 14:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 11, 08:002016-08-11 08:00:00 UTC2016-08-11 09:00:00 UTC101
Aug 11, 09:002016-08-11 09:00:00 UTC2016-08-11 10:00:00 UTC000
Aug 11, 10:002016-08-11 10:00:00 UTC2016-08-11 11:00:00 UTC000
Aug 11, 11:002016-08-11 11:00:00 UTC2016-08-11 12:00:00 UTC000
Aug 11, 12:002016-08-11 12:00:00 UTC2016-08-11 13:00:00 UTC000
Aug 11, 13:002016-08-11 13:00:00 UTC2016-08-11 14:00:00 UTC000
Aug 11, 14:002016-08-11 14:00:00 UTC2016-08-11 15:00:00 UTC101

What Hacker News says

2 sources
We put these tests together after clients with existing Rails stacks wanted our input on choosing Phoenix or Rails for their specific real-time push features. The benchmark apps are simple – no database, no sessions, but we wanted to set the PubSub patterns up in a way that would give us insights into a wide range of applications. The blog repo contains everything to setup an instance and run the benchmarks yourself: https://github.com/chrismccord/channelsac
In Phoenix Channels vs. Rails ActionCable
Written by Chris McCord the creator of Phoenix. His summary when comparing to Rails for real-time push notifications is below. "... the sweet-spot for Action Cable today is small workloads with few subscribers on any given topic. Going beyond this means engineering efforts and resources must be spent on managing multiple nodes and optimizing code out of channels. Higher workloads with broadcasts to more than a few dozen subscribers risks availability. With Phoenix, we've shown that channels performance remains consistent as notification demand increases, which is essential for handling traffic spikes and avoiding overload." Source code: https://github.com/chrismccord/channelsac
In Phoenix Channels vs. Rails Action Cable

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.