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
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
|
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="">
<meta name="author" content="Loïc Hoguin based on a design from (Soft10) Pol Cámara">
<meta name="generator" content="Hugo 0.37.1" />
<title>Nine Nines: Erlang Scalability</title>
<link href='https://fonts.googleapis.com/css?family=Open+Sans:400,700,400italic' rel='stylesheet' type='text/css'>
<link href="/css/99s.css?r=1" rel="stylesheet">
<link rel="shortcut icon" href="/img/ico/favicon.ico">
<link rel="apple-touch-icon-precomposed" sizes="114x114" href="/img/ico/apple-touch-icon-114.png">
<link rel="apple-touch-icon-precomposed" sizes="72x72" href="/img/ico/apple-touch-icon-72.png">
<link rel="apple-touch-icon-precomposed" href="/img/ico/apple-touch-icon-57.png">
</head>
<body class="">
<header id="page-head">
<div id="topbar" class="container">
<div class="row">
<div class="span2">
<h1 id="logo"><a href="/" title="99s">99s</a></h1>
</div>
<div class="span10">
<div id="side-header">
<nav>
<ul>
<li class="active"><a title="Hear my thoughts" href="/articles">Articles</a></li>
<li><a title="Watch my talks" href="/talks">Talks</a></li>
<li><a title="Read the docs" href="/docs">Documentation</a></li>
<li><a title="Request my services" href="/services">Consulting & Training</a></li>
</ul>
</nav>
<ul id="social">
<li>
<a href="https://github.com/ninenines" title="Check my Github repositories"><img src="/img/ico_github.png" data-hover="/img/ico_github_alt.png" alt="Github"></a>
</li>
<li>
<a title="Contact me" href="mailto:[email protected]"><img src="/img/ico_mail.png" data-hover="/img/ico_mail_alt.png"></a>
</li>
</ul>
</div>
</div>
</div>
</div>
</header>
<div id="contents">
<div class="container">
<div class="row">
<div class="span9 maincol">
<article class="blog_item">
<header>
<h1 class="lined-header"><span>Erlang Scalability</span></h1>
<p class="date">
<span class="day">18</span>
<span class="month">Feb</span>
</p>
</header>
<div class="paragraph"><p>I would like to share some experience and theories on
Erlang scalability.</p></div>
<div class="paragraph"><p>This will be in the form of a series of hints, which
may or may not be accompanied with explanations as to why
things are this way, or how they improve or reduce the scalability
of a system. I will try to do my best to avoid giving falsehoods,
even if that means a few things won’t be explained.</p></div>
<div class="sect1">
<h2 id="_nifs">NIFs</h2>
<div class="sectionbody">
<div class="paragraph"><p>NIFs are considered harmful. I don’t know any single NIF-based
library that I would recommend. That doesn’t mean they should
all be avoided, just that if you’re going to want your system to
scale, you probably shouldn’t use a NIF.</p></div>
<div class="paragraph"><p>A common case for using NIFs is JSON processing. The problem
is that JSON is a highly inefficient data structure (similar
in inefficiency to XML, although perhaps not as bad). If you can
avoid using JSON, you probably should. MessagePack can replace
it in many situations.</p></div>
<div class="paragraph"><p>Long-running NIFs will take over a scheduler and prevent Erlang
from efficiently handling many processes.</p></div>
<div class="paragraph"><p>Short-running NIFs will still confuse the scheduler if they
take more than a few microseconds to run.</p></div>
<div class="paragraph"><p>Threaded NIFs, or the use of the <code>enif_consume_timeslice</code>
might help allievate this problem, but they’re not a silver bullet.</p></div>
<div class="paragraph"><p>And as you already know, a crashing NIF will take down your VM,
destroying any claims you may have at being scalable.</p></div>
<div class="paragraph"><p>Never use a NIF because "C is fast". This is only true in
single-threaded programs.</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_bifs">BIFs</h2>
<div class="sectionbody">
<div class="paragraph"><p>BIFs can also be harmful. While they are generally better than
NIFs, they are not perfect and some of them might have harmful
effects on the scheduler.</p></div>
<div class="paragraph"><p>A great example of this is the <code>erlang:decode_packet/3</code>
BIF, when used for HTTP request or response decoding. Avoiding
its use in <em>Cowboy</em> allowed us to see a big increase in
the number of requests production systems were able to handle,
up to two times the original amount. Incidentally this is something
that is impossible to detect using synthetic benchmarks.</p></div>
<div class="paragraph"><p>BIFs that return immediately are perfectly fine though.</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_binary_strings">Binary strings</h2>
<div class="sectionbody">
<div class="paragraph"><p>Binary strings use less memory, which means you spend less time
allocating memory compared to list-based strings. They are also
more natural for strings manipulation because they are optimized
for appending (as opposed to prepending for lists).</p></div>
<div class="paragraph"><p>If you can process a binary string using a single match context,
then the code will run incredibly fast. The effects will be much
increased if the code was compiled using HiPE, even if your Erlang
system isn’t compiled natively.</p></div>
<div class="paragraph"><p>Avoid using <code>binary:split</code> or <code>binary:replace</code>
if you can avoid it. They have a certain overhead due to supporting
many options that you probably don’t need for most operations.</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_buffering_and_streaming">Buffering and streaming</h2>
<div class="sectionbody">
<div class="paragraph"><p>Use binaries. They are great for appending, and it’s a direct copy
from what you receive from a stream (usually a socket or a file).</p></div>
<div class="paragraph"><p>Be careful to not indefinitely receive data, as you might end up
having a single binary taking up huge amounts of memory.</p></div>
<div class="paragraph"><p>If you stream from a socket and know how much data you expect,
then fetch that data in a single <code>recv</code> call.</p></div>
<div class="paragraph"><p>Similarly, if you can use a single <code>send</code> call, then
you should do so, to avoid going back and forth unnecessarily between
your Erlang process and the Erlang port for your socket.</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_list_and_binary_comprehensions">List and binary comprehensions</h2>
<div class="sectionbody">
<div class="paragraph"><p>Prefer list comprehensions over <code>lists:map/2</code>. The
compiler will be able to optimize your code greatly, for example
not creating the result if you don’t need it. As time goes on,
more optimizations will be added to the compiler and you will
automatically benefit from them.</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_gen_server_is_no_silver_bullet">gen_server is no silver bullet</h2>
<div class="sectionbody">
<div class="paragraph"><p>It’s a bad idea to use <code>gen_server</code> for everything.
For two reasons.</p></div>
<div class="paragraph"><p>There is an overhead everytime the <code>gen_server</code> receives
a call, a cast or a simple message. It can be a problem if your
<code>gen_server</code> is in a critical code path where speed
is all that matters. Do not hesitate to create other kinds of
processes where it makes sense. And depending on the kind of process,
you might want to consider making them special processes, which
would essentially behave the same as a <code>gen_server</code>.</p></div>
<div class="paragraph"><p>A common mistake is to have a unique <code>gen_server</code> to
handle queries from many processes. This generally becomes the
biggest bottleneck you’ll want to fix. You should try to avoid
relying on a single process, using a pool if you can.</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_supervisor_and_monitoring">Supervisor and monitoring</h2>
<div class="sectionbody">
<div class="paragraph"><p>A <code>supervisor</code> is also a <code>gen_server</code>,
so the previous points also apply to them.</p></div>
<div class="paragraph"><p>Sometimes you’re in a situation where you have supervised
processes but also want to monitor them in one or more other
processes, effectively duplicating the work. The supervisor
already knows when processes die, why not use this to our
advantage?</p></div>
<div class="paragraph"><p>You can create a custom supervisor process that will perform
both the supervision and handle exit and other events, allowing
to avoid the combination of supervising and monitoring which
can prove harmful when many processes die at once, or when you
have many short lived processes.</p></div>
</div>
</div>
<div class="sect1">
<h2 id="_ets_for_lolspeed_tm">ets for LOLSPEED(tm)</h2>
<div class="sectionbody">
<div class="paragraph"><p>If you have data queried or modified by many processes, then
<code>ets</code> public or protected tables will give you the
performance boost you require. Do not forget to set the
<code>read_concurrency</code> or <code>write_concurrency</code>
options though.</p></div>
<div class="paragraph"><p>You might also be thrilled to know that Erlang R16B will feature
a big performance improvement for accessing <code>ets</code> tables
concurrently.</p></div>
</div>
</div>
</article>
</div>
<div class="span3 sidecol">
<h3>More articles</h3>
<ul id="articles-nav" class="extra_margin">
<li><a href="https://ninenines.eu/articles/cowboy-2.4.0/">Cowboy 2.4</a></li>
<li><a href="https://ninenines.eu/articles/cowboy-2.3.0/">Cowboy 2.3</a></li>
<li><a href="https://ninenines.eu/articles/cowboy-2.2.0/">Cowboy 2.2</a></li>
<li><a href="https://ninenines.eu/articles/cowboy-2.1.0/">Cowboy 2.1</a></li>
<li><a href="https://ninenines.eu/articles/cowboy-2.0.0/">Cowboy 2.0</a></li>
<li><a href="https://ninenines.eu/articles/cowboy-2.0.0-rc.2/">Cowboy 2.0 release candidate 2</a></li>
<li><a href="https://ninenines.eu/articles/cowboy-2.0.0-rc.1/">Cowboy 2.0 release candidate 1</a></li>
<li><a href="https://ninenines.eu/articles/the-elephant-in-the-room/">The elephant in the room</a></li>
<li><a href="https://ninenines.eu/articles/dont-let-it-crash/">Don't let it crash</a></li>
<li><a href="https://ninenines.eu/articles/cowboy-2.0.0-pre.4/">Cowboy 2.0 pre-release 4</a></li>
<li><a href="https://ninenines.eu/articles/ranch-1.3/">Ranch 1.3</a></li>
<li><a href="https://ninenines.eu/articles/ml-archives/">Mailing list archived</a></li>
<li><a href="https://ninenines.eu/articles/website-update/">Website update</a></li>
<li><a href="https://ninenines.eu/articles/erlanger-playbook-september-2015-update/">The Erlanger Playbook September 2015 Update</a></li>
<li><a href="https://ninenines.eu/articles/erlanger-playbook/">The Erlanger Playbook</a></li>
<li><a href="https://ninenines.eu/articles/erlang-validate-utf8/">Validating UTF-8 binaries with Erlang</a></li>
<li><a href="https://ninenines.eu/articles/on-open-source/">On open source</a></li>
<li><a href="https://ninenines.eu/articles/the-story-so-far/">The story so far</a></li>
<li><a href="https://ninenines.eu/articles/cowboy2-qs/">Cowboy 2.0 and query strings</a></li>
<li><a href="https://ninenines.eu/articles/january-2014-status/">January 2014 status</a></li>
<li><a href="https://ninenines.eu/articles/farwest-funded/">Farwest got funded!</a></li>
<li><a href="https://ninenines.eu/articles/erlang.mk-and-relx/">Build Erlang releases with Erlang.mk and Relx</a></li>
<li><a href="https://ninenines.eu/articles/xerl-0.5-intermediate-module/">Xerl: intermediate module</a></li>
<li><a href="https://ninenines.eu/articles/xerl-0.4-expression-separator/">Xerl: expression separator</a></li>
<li><a href="https://ninenines.eu/articles/erlang-scalability/">Erlang Scalability</a></li>
<li><a href="https://ninenines.eu/articles/xerl-0.3-atomic-expressions/">Xerl: atomic expressions</a></li>
<li><a href="https://ninenines.eu/articles/xerl-0.2-two-modules/">Xerl: two modules</a></li>
<li><a href="https://ninenines.eu/articles/xerl-0.1-empty-modules/">Xerl: empty modules</a></li>
<li><a href="https://ninenines.eu/articles/ranch-ftp/">Build an FTP Server with Ranch in 30 Minutes</a></li>
<li><a href="https://ninenines.eu/articles/tictactoe/">Erlang Tic Tac Toe</a></li>
</ul>
<h3>Feedback</h3>
<p>Feel free to <a href="mailto:[email protected]">email us</a>
if you found any mistake or need clarification on any of the
articles.</p>
</div>
</div>
</div>
</div>
<footer>
<div class="container">
<div class="row">
<div class="span6">
<p id="scroll-top"><a href="#">↑ Scroll to top</a></p>
<nav>
<ul>
<li><a href="mailto:[email protected]" title="Contact us">Contact us</a></li><li><a href="https://github.com/ninenines/ninenines.github.io" title="Github repository">Contribute to this site</a></li>
</ul>
</nav>
</div>
<div class="span6 credits">
<p><img src="/img/footer_logo.png"></p>
<p>Copyright © Loïc Hoguin 2012-2018</p>
</div>
</div>
</div>
</footer>
<script src="/js/custom.js"></script>
</body>
</html>
|
