[Erlang 0126] the Erlang paper we have read

Source: Internet
Author: User

I launched a collection activity [LINK] On the Erlang resources Douban website, "[Collection] the Erlang papers we have read". I hope you will come and join us. the purpose of initiating such an activity is that there are very few Erlang-related publications, and most of the time they are looking for answers from academic papers. Finding the right papers is the first step. This activity aims to solve this problem.

 

In a very small knowledge point, there may be a wonderful paper for you to analyze, strip, or even piece together a complete Erlang knowledge system. Let's get started...

 

 

Building A Reliable Distributed System for software errors

Making reliable distributed systems in the presence of sodware errors

Address: http://pubftp0.availo.se/pub/FreeBSD/distfiles/erlang-doc/r13b01/armstrong_thesis_2003.pdf

Http://man.lupaworld.com/content/other/erlang.pdf.

Note: There is nothing to say. This paper is almost a must-read for getting started with Erlang. It can even complete the basic knowledge of Erlang;

 

Concurrent Programming in Erlang

Address: http://www.erlang.org/download/erlang-book-part1.pdf

Note: textbooks

Characterizing the scalability of Erlang VM on executor-core processors

Address: http://kth.diva-portal.org/smash/get/diva2:392243/FULLTEXT01

Note: It is estimated that this article is a must-read article for understanding Erlang VM. This article is displayed everywhere in many blogs involving the implementation of Erlang VM;

 

Changing ing alternative memory ubuntures for Erlang: implementation and performance evaluation

Address: http://www.fantasi.se/publications/Wilhelmsson_MSc.pdf

Note: This article introduces Erlang VM garbage collection and memory management.

 


Ef? Cient memory management for concurrent programs that use message passing I, II

Address: http://user.it.uu.se /~ Kostis/papers/scp_mm.pdf

Note: Erlang VM memory management GC

 

Heap ubuntures for concurrent limits ages using message passing
Address: http://www.fantasi.se/publications/ISMM02.pdf

Abstract: We discuss alternative heap ubuntures for versions that rely on automatic memory management and implement con-
Currency through asynchronous message passing. We describe how Interprocess Communication and garbage collec-
Tion happens in each architecture, and extensively discuss the tradeo? S that are involved. In an implementation set-
Ting (the Erlang/OTP system) where the rest of the runtime system is unchanged, we present a detailed experimental
Comparison between these ubuntures using both synthetic programs and large extends cial products as benchmarks.
Note: To sum up one sentence, this article is: what essentially happens when a message is transmitted

 

 

On preserving term sharing in the Erlang Virtual Machine

Address: http://user.it.uu.se /~ Kostis/papers/erlang12_sharing.pdf

Abstract: In this paper we describe our experiences and argue through examples why? Attening terms during copying is not a good idea

A language like Erlang. More importantly, we propose a sharing preserving copying mechanic for Erlang/OTP and describe a pub-

Licly available complete implementation of this mechanism.

 

Bit-level binaries and generalized comprehensions in Erlang
Address: http://user.it.uu.se /~ Pergu/papers/erlang05.pdf

Note: To further simplify programming on bit streams we then show how binary comprehensions can be introduced in the language and how binary and list comprehensions can be extended to allow both binary and list generators.


An Introduction to core Erlang
Http://citeseerx.ist.psu.edu/viewdoc/download;jsessionid=1C8691982F56D28905DAC4D731A386C7? Doi = 10.1.1.3167146 & rep = rep1 & type = pdf remarks: describes the relationship between core Erlang and Erlang, how is the process of analyzing and transforming the development history from Erlang code to core Erlang code greatly simplified.
Programming Ef? Ciently with binaries and bit stringsAddress: http://www.erlang.org/euc/07/papers/1700gustafsson. Abstract: This paper will describe the new additions to the language and show how they can be used Ef? Ciently given the new optimizationsof binary pattern matching and binary construction. It also has des some performance numbers to give an idea of the gains that can be
Made with the new optimizations. Note: Erlang efficiency guide tells you how, this paper tells you why Programming distributed Erlang applications: pitfalls and recipes
Programming distributed Erlang program: trap and countermeasure address: http://man.lupaworld.com/content/develop/p37-svensson.pdf remarks: basic message passing assurance-stream semantics cross-node programming trap PID repeat message order Parameterized modules in ErlangAddress: plugin has become a legend. in the latest version of Erlang, you need to use this feature through plug-in projects. Design Patterns for simulations in Erlang/OTPAddress: Skip the sections that are not of interest to explain. This article describes the implemented behaviours. Extended process registry for ErlangAddress: http://svn.ulf.wiger.net/gproc/doc/erlang07-wiger.pdf address: http://www.erlang.se/workshop/2007/proceedings/02wier.#note: gproc: extended process registry this should be a lot of people in practice   Troubleshooting a large Erlang SystemAddress: http://www.erlang.se/workshop/2004/cronqvist.#note: describes how to use the OTP troubleshooting tool set. Static detection of race conditions in ErlangAddress: Must we address the problem of detecting some commonly occurring kinds of race conditions in Erlang programs using static analy-

Sis.

 

Erlang's exception handling Revisited

Address: http://www.erlang.se/workshop/2004/exception.pdf

Abstract: we give a comprehensive description of the behaviour of specified tions in modern-day Erlang, present a theoretical model of
Semantics of exceptions, and use this to derive the New Try-construct.

Cleaning up Erlang code is a dirty job but somebody's gotta do itAddress:  Http://users.ece.cmu.edu /~ Aavgerin/papers/erlang09.pdf note: we do not have to use this automatic code optimization tool to read this paper. What's more valuable is to ask how & why Build your next web application with ErlangAddress: http://www.kth.se/polopoly_fs/1.162674! /Menu/General/column-content/attachment/ieee20.note: if there is an oracle, remember the booklet. Skip this article. A Study of Erlang ETS table implementations and PerformanceAddress: http://www.erlang.org/workshop/2003/paper/p43-fritchie.pdf Summary: the viability of implementing an in-memory database, Erlang ETS, using a relatively-new data structure, called a Judy array, was studied by comparing the performance of ETS tables based on four data structures: AVL balanced binary trees, B-trees, resizable linear hash tables, and Judy arrays. A stream library using Erlang BinariesAddress: please this paper introduces the memory and behavior characteristics of lists, tuples and binaries in Erlang, then continues with a de-

Sort of the bit syntax and standard methods of using binaries to deal with streamed data. Next it introduces BIF functions that
Are shown to be much faster than using the traditional BIT syntax to manipulate binary data.

 

A Scalability benchmark suite for Erlang/OTP

Address: http://www.softlab.ntua.gr /~ Gtsiour/files/erlang01-aronis.pdf

Abstract: This paper presents the main aspects of the design and the current status of bencherl, a publicly available scalability Benchmark

Suite for applications written in Erlang.

 

All you wanted to know about the hipe Compiler (but might have been afraid to ask)

Address: http://user.it.uu.se /~ Pergu/papers/erlang03.pdf

Remarks: Answers almost all common questions about hipe.

 

 

No more need for records

Address: http://www.cs.otago.ac.nz/staffpriv/ OK /frames.pdf

Note: The trade-off between the origin design of the maps structure is very interesting.

 

 

 

Unfinished, to be continued

 

[Erlang 0126] the Erlang paper we have read

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.