在以前的文章 elixir! #0061 高负载高并发问题的万能钥匙 ---- 队列(queue) 中,咱们介绍了如何使用队列来避免 server 在收到多个耗时较长的 call 请求时被阻塞住 mailbox。今天咱们再来讨论一下另外一种常见的消息传递模式 —— PubSub。segmentfault
PubSub 和消息队列很是相似,主要的区别是 PubSub 通常适用于同一个消息有多个消费者同时关注的场景。例如,多人在线的直播间,电商实时更新的库存信息等等。比较侧重于性能,而非消息的到达。相同之处在于消息的生产者和消费者是相互解耦的,消息是发送到某个 topic 里,而非直接发给对方,因此生产者的负担会减少。消息可能会须要有一个保存机制,多是持久化地保存到硬盘上,也多是只在内存中停留一段时间,也多是直接发送,不作任何持久化,这样不在线的消费者就会丢失消息。并发
PubSub 的本质是职责的分离:生产者的职责是要准确地生产消息,把消息投递到正确的 topic,而不用去关心谁会读到这个消息。同时,消费者也不用关心是谁生产了这个消息,而只须要关注消息的 topic 和内容。高并发
因此 PubSub server 的职责就是将消息投递给 topic 的关注者们。这是一个时间复杂度 O(n)
的操做,咱们始终须要遍历某个 topic 的 subscriber 列表。此外,对某个topic 的关注者列表,会须要作常常的修改:新增关注,取消关注,掉线,都须要增长或者删除列表的内容,若是一个 topic 有上万个关注者,就应该考虑这些操做的耗时。性能
这里实现了一个超简易的 pubsub:测试
defmodule M6 do use GenServer def start do GenServer.start(__MODULE__, :ok) end def pub(server, topic, msg) do GenServer.call(server, {:pub, topic, msg}) end def sub(server, topic) do GenServer.call(server, {:sub, topic}) end def unsub(server, topic) do GenServer.call(server, {:unsub, topic}) end @impl true def init(_) do {:ok, %{topics: %{}}} end @impl true def handle_call({:pub, topic, msg}, _from, state) do case state.topics do %{^topic => topic_state} -> broadcast(topic_state, msg) _ -> nil end {:reply, :ok, state} end def handle_call({:sub, topic}, {pid, _ref}, %{topics: topics} = state) do _monitor_ref = Process.monitor(pid) topic_state = case state.topics do %{^topic => topic_state} -> topic_state _ -> MapSet.new() end {:reply, :ok, %{state | topics: Map.put(topics, topic, add_client(topic_state, pid))}} end def handle_call({:unsub, topic}, {pid, _ref}, %{topics: topics} = state) do topic_state = case state.topics do %{^topic => topic_state} -> topic_state _ -> %{} end {:reply, :ok, %{state | topics: Map.put(topics, topic, delete_client(topic_state, pid))}} end @impl true def handle_info({:DOWN, _ref, :process, pid, _}, state) do topics = Enum.reduce(state.topics, %{}, fn {t, ts}, acc -> Map.put(acc, t, delete_client(ts, pid)) end) {:noreply, %{state | topics: topics}} end defp add_client(topic_state, client) do MapSet.put(topic_state, client) end defp delete_client(topic_state, client) do MapSet.delete(topic_state, client) end defp broadcast(topic_state, msg) do Enum.each(topic_state, fn pid -> send(pid, msg) end) end end
测试一下:spa
iex(30)> {:ok, s} = M6.start {:ok, #PID<0.216.0>} iex(31)> :sys.trace s, true :ok iex(32)> M6.sub s, "jobs" *DBG* <0.216.0> got call {sub,<<"jobs">>} from <0.149.0> *DBG* <0.216.0> sent ok to <0.149.0>, new state #{topics => #{<<"jobs">> => #{'__struct__' => 'Elixir.MapSet', map => #{<0.149.0> => []}, version => 2}}} :ok iex(33)> spawn(fn -> M6.pub(s, "jobs", "backend engineer") end) *DBG* <0.216.0> got call {pub,<<"jobs">>,<<"backend engineer">>} from <0.220.0> #PID<0.220.0> *DBG* <0.216.0> sent ok to <0.220.0>, new state #{topics => #{<<"jobs">> => #{'__struct__' => 'Elixir.MapSet', map => #{<0.149.0> => []}, version => 2}}} iex(34)> flush "backend engineer" :ok iex(35)> M6.unsub s, "jobs" *DBG* <0.216.0> got call {unsub,<<"jobs">>} from <0.149.0> *DBG* <0.216.0> sent ok to <0.149.0>, new state #{topics => #{<<"jobs">> => #{'__struct__' => 'Elixir.MapSet', map => #{}, version => 2}}} :ok