blob: dc7d3c25712252001a15c0c7353d16d434b96052 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<HEAD>
<TITLE> [99s-extend] tring to understand ranch_conns_sup
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20tring%20to%20understand%20ranch_conns_sup&In-Reply-To=%3C53B50C61.9050601%40ninenines.eu%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="000405.html">
<LINK REL="Next" HREF="000407.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[99s-extend] tring to understand ranch_conns_sup</H1>
<B>Loïc Hoguin</B>
<A HREF="mailto:extend%40lists.ninenines.eu?Subject=Re%3A%20%5B99s-extend%5D%20tring%20to%20understand%20ranch_conns_sup&In-Reply-To=%3C53B50C61.9050601%40ninenines.eu%3E"
TITLE="[99s-extend] tring to understand ranch_conns_sup">essen at ninenines.eu
</A><BR>
<I>Thu Jul 3 09:55:13 CEST 2014</I>
<P><UL>
<LI>Previous message: <A HREF="000405.html">[99s-extend] tring to understand ranch_conns_sup
</A></li>
<LI>Next message: <A HREF="000407.html">[99s-extend] [cowboy REST] returning {true, URL} to PUT
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#406">[ date ]</a>
<a href="thread.html#406">[ thread ]</a>
<a href="subject.html#406">[ subject ]</a>
<a href="author.html#406">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>Have you observed ranch_conns_sup be a bottleneck? In practice it
shouldn't be.
On 07/03/2014 09:40 AM, Adel Zhang wrote:
><i> Ranch uses a tcp acceptor pool to accept connections concurrently. But
</I>><i> the acceptor process
</I>><i> needs to wait for the *only one* ranch_conns_sup spawning the protocol
</I>><i> process.
</I>><i>
</I>><i> Is ranch_conns_sup maybe a bottleneck?
</I>><i>
</I>><i> Thanks.
</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="https://lists.ninenines.eu/listinfo/extend">https://lists.ninenines.eu/listinfo/extend</A>
</I>
--
Loïc Hoguin
<A HREF="http://ninenines.eu">http://ninenines.eu</A>
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="000405.html">[99s-extend] tring to understand ranch_conns_sup
</A></li>
<LI>Next message: <A HREF="000407.html">[99s-extend] [cowboy REST] returning {true, URL} to PUT
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#406">[ date ]</a>
<a href="thread.html#406">[ thread ]</a>
<a href="subject.html#406">[ subject ]</a>
<a href="author.html#406">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://lists.ninenines.eu/listinfo/extend">More information about the Extend
mailing list</a><br>
</body></html>
|