diff options
Diffstat (limited to 'archives/extend/2013-April/000103.html')
-rw-r--r-- | archives/extend/2013-April/000103.html | 122 |
1 files changed, 122 insertions, 0 deletions
diff --git a/archives/extend/2013-April/000103.html b/archives/extend/2013-April/000103.html new file mode 100644 index 00000000..28c7c536 --- /dev/null +++ b/archives/extend/2013-April/000103.html @@ -0,0 +1,122 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML> + <HEAD> + <TITLE> [99s-extend] Distributed model? + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Distributed%20model%3F&In-Reply-To=%3C4011ABA6-BD55-4DEB-BE8F-2E20F2376A25%40gmail.com%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <style type="text/css"> + pre { + white-space: pre-wrap; /* css-2.1, curent FF, Opera, Safari */ + } + </style> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="000102.html"> + <LINK REL="Next" HREF="000104.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[99s-extend] Distributed model?</H1> + <B>Lee Sylvester</B> + <A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20Distributed%20model%3F&In-Reply-To=%3C4011ABA6-BD55-4DEB-BE8F-2E20F2376A25%40gmail.com%3E" + TITLE="[99s-extend] Distributed model?">lee.sylvester at gmail.com + </A><BR> + <I>Thu Apr 11 17:46:35 CEST 2013</I> + <P><UL> + <LI>Previous message: <A HREF="000102.html">[99s-extend] Distributed model? +</A></li> + <LI>Next message: <A HREF="000104.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#103">[ date ]</a> + <a href="thread.html#103">[ thread ]</a> + <a href="subject.html#103">[ subject ]</a> + <a href="author.html#103">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>Okay, so I've figured it out. I will need to have a separate messaging layer. Does anyone know of a messaging layer that can be used when all you know is the PID to send to? + +Thanks, +Lee + + + +On 11 Apr 2013, at 13:55, Lee Sylvester <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: + +><i> Thank you, Jeremy, that's good advice. It's not so much a chat platform, but I guess it would resemble one in architecture. The part I'm concerned about, though, is should I be avoiding the internal Erlang messaging between connections (over many nodes) for heavy messaging? +</I>><i> +</I>><i> Thanks, +</I>><i> Lee +</I>><i> +</I>><i> +</I>><i> +</I>><i> On 11 Apr 2013, at 08:04, Jeremy Ong <<A HREF="https://lists.ninenines.eu/listinfo/extend">jeremy at quarkgames.com</A>> wrote: +</I>><i> +</I>>><i> I see. I assume this is for a chat server of some sort? +</I>>><i> +</I>>><i> You don't want the user process sending all these messages because the +</I>>><i> user process wouldn't be able to do anything useful (like receive +</I>>><i> messages) in the meantime. +</I>>><i> +</I>>><i> Better is to implement a pubsub process for each channel of +</I>>><i> communication (i.e. one process per room) or rely on Redis pubsub or +</I>>><i> something if speed is extremely important. +</I>>><i> +</I>>><i> There is no way to get around the O(N) complexity of broadcasting. +</I>>><i> +</I>>><i> On Wed, Apr 10, 2013 at 11:49 PM, Lee Sylvester <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: +</I>>>><i> Thanks Jeremy, but what about inter-node communication? If I have a user on node A sending a message to 10k users located on 10 other nodes, what is the best way to handle that? Especially if this user is sending several messages and expecting replies. Should I use the standard Erlang inter-process messaging or should I implement an MQ on top to handle this? +</I>>>><i> +</I>>>><i> Thanks, +</I>>>><i> Lee +</I>>>><i> +</I>>>><i> +</I>>>><i> On 11 Apr 2013, at 07:29, Jeremy Ong <<A HREF="https://lists.ninenines.eu/listinfo/extend">jeremy at quarkgames.com</A>> wrote: +</I>>>><i> +</I>>>>><i> Make all the machines identically and add an haproxy (or equivalent) +</I>>>>><i> machine to load balance between all of them. Haproxy can handle many +</I>>>>><i> many requests. Keep in mind that with tcp, the load balancer is just +</I>>>>><i> accepting the socket but then the client communicates with the actual +</I>>>>><i> application server directly afterwards. +</I>>>>><i> +</I>>>>><i> On Wed, Apr 10, 2013 at 10:51 PM, Lee Sylvester <<A HREF="https://lists.ninenines.eu/listinfo/extend">lee.sylvester at gmail.com</A>> wrote: +</I>>>>>><i> Hi guys, +</I>>>>>><i> +</I>>>>>><i> So, I have my Cowboy / Bullet server working nicely, now, with much thanks to members on this list. I'm now looking at the best means of clustering this app. I want to set this up so that, should the connection count get very high (which it will), then I should only have to throw more machines at this problem and it'll all go away. +</I>>>>>><i> +</I>>>>>><i> I've got most of the logic working for this, but what I'm worried about is sending a lot of content over the erlang inter-node connection. I've heard hogging this line can be both a bottleneck and can potentially interrupt the heartbeat between nodes. With this in mind, should I look at adding a ZMQ layer or some such to facilitate this? What is the general solution to high traffic between nodes? +</I>>>>>><i> +</I>>>>>><i> Thanks, +</I>>>>>><i> Lee +</I>>>>>><i> _______________________________________________ +</I>>>>>><i> Extend mailing list +</I>>>>>><i> <A HREF="https://lists.ninenines.eu/listinfo/extend">Extend at lists.ninenines.eu</A> +</I>>>>>><i> <A HREF="http://lists.ninenines.eu:81/listinfo/extend">http://lists.ninenines.eu:81/listinfo/extend</A> +</I>>>><i> +</I>><i> +</I> + +</PRE> + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="000102.html">[99s-extend] Distributed model? +</A></li> + <LI>Next message: <A HREF="000104.html">[99s-extend] populating #http_req for unit testing +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#103">[ date ]</a> + <a href="thread.html#103">[ thread ]</a> + <a href="subject.html#103">[ subject ]</a> + <a href="author.html#103">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend +mailing list</a><br> +</body></html> |