DOCSLIB.ORG

Corobase: Coroutine-Oriented Main-Memory Database Engine

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Corobase: Coroutine-Oriented Main-Memory Database Engine CoroBase: Coroutine-Oriented Main-Memory Database Engine Yongjun He Jiacheng Lu Tianzheng Wang Simon Fraser University Simon Fraser University Simon Fraser University [email protected] [email protected] [email protected] ABSTRACT transaction: transaction: transaction: v1 = get(k1) v1, v2 = v1 = get(k1) Data stalls are a major overhead in main-memory database engines v2 = get(k2) multi_get(k1, k2) v2 = get(k2) due to the use of pointer-rich data structures. Lightweight corou- if v1 == 0: if v1 == 0: if v1 == 0: tines ease the implementation of software prefetching to hide data put(k3, 10) put(k3, 10) put(k3, 10) stalls by overlapping computation and asynchronous data prefetch- T1 T1 T1 T2 . T1 T1 T1 T2 T2 T1 T1 T1 . ing. Prior solutions, however, mainly focused on (1) individual . Time T1 T1 T2 T2 T2 T2 components and operations and (2) intra-transaction batching that (a) Sequential (b) Multi-get (c) CoroBase requires interface changes, breaking backward compatibility. It was not clear how they apply to a full database engine and how much Figure 1: Data access interfaces and execution under (a) se- end-to-end beneft they bring under various workloads. quential execution (no interleaving), (b) prior approaches This paper presents CoroBase, a main-memory database engine that require multi-key interfaces, (c) CoroBase which hides that tackles these challenges with a new coroutine-to-transaction par- data stalls and maintains backward compatibility. adigm. Coroutine-to-transaction models transactions as coroutines and thus enables inter-transaction batching, avoiding application changes but retaining the benefts of prefetching. We show that bring data from memory to CPU caches. This gave rise to software × on a 48-core server, CoroBase can perform close to 2 better for prefetching techniques [5, 21, 26, 34, 39, 44, 45] that hide memory read-intensive workloads and remain competitive for workloads access latency by overlapping data fetching and computation, allevi- that inherently do not beneft from software prefetching. ating pointer chasing overhead. Most of these techniques, however, require hand-crafting asynchronous/pipelined algorithms or state PVLDB Reference Format: machines to be able to suspend/resume execution as needed. This is Yongjun He, Jiacheng Lu, and Tianzheng Wang. CoroBase: Coroutine-Oriented Main-Memory Database Engine. PVLDB, 14(3): a difcult and error-prone process; the resulted code often deviates 431-444, 2021. a lot from the original code, making it hard to maintain [21]. doi:10.14778/3430915.3430932 1.1 Software Prefetching via Coroutines PVLDB Artifact Availability: With the recent standardization in C++20 [19], coroutines greatly The source code, data, and/or other artifacts have been made available at ease the implementation of software prefetching. Coroutines [38] htps://github.com/sfu-dis/corobase/tree/v1.0. are functions that can suspend voluntarily and be resumed later. Functions that involve pointer chasing can be written as coroutines 1 INTRODUCTION which are executed (interleaved) in batches. Before dereferencing Modern main-memory database engines [11, 22, 24, 25, 30, 33, 56, a pointer in coroutine �1, the thread issues a prefetch followed 59] use memory-optimized data structures [2, 29, 31, 36] to ofer by a suspend to pause �1 and switches to another coroutine �2, high performance on multicore CPUs. Many such data structures overlapping data fetching in �1 and computation in �2. rely on pointer chasing [34] which can stall the CPU upon cache Compared to earlier approaches [5, 26], coroutines only require misses. For example, in Figure 1(a), to execute two SELECT (get) prefetch/suspend be inserted into sequential code, greatly simpli- queries, the engine may traverse a tree, and if a needed tree node fying implementation while delivering high performance, as the is not cache-resident, dereferencing a pointer to it stalls the CPU switching overhead can be cheaper than a last-level cache miss [21]. (dotted box in the fgure) to fetch the node from memory. Compu- However, adopting software prefetching remains challenging. tation (solid box) would not resume until data is in the cache. With First, existing approaches typically use intra-transaction batch- the wide speed gap between CPU and memory, memory accesses ing which mandates multi-key interfaces that can break backward have become a major overhead [4, 35]. The emergence of capacious compatibility. For example, in Figure 1(b) an application1 uses but slower persistent memory [10] is further widening this gap. multi_get to retrieve a batch of records at once in a transac- Modern processors allow multiple outstanding cache misses tion. Cache misses caused by probing k1 (k2) in a tree are hid- and provide prefetch instructions [18] for software to explicitly den behind the computation part of probing k2 (k1). While intra- transaction batching is a natural ft for some operators (e.g., IN- This work is licensed under the Creative Commons BY-NC-ND 4.0 International License. Visit htps://creativecommons.org/licenses/by-nc-nd/4.0/ to view a copy of predicate queries [44, 45]), it is not always directly applicable. this license. For any use beyond those covered by this license, obtain permission by Changing the application is not always feasible and may not achieve emailing [email protected]. Copyright is held by the owner/author(s). Publication rights the desired improvement as depending requests need to be issued in licensed to the VLDB Endowment. Proceedings of the VLDB Endowment, Vol. 14, No. 3 ISSN 2150-8097. doi:10.14778/3430915.3430932 1The “application” may be another database system component or an end-user appli- cation that uses the record access interfaces provided by the database engine. 431 separate batches, limiting interleaving opportunities. Short (or even necessitating new interfaces, and (2) understand its end-to-end single-record) transactions also cannot beneft much due to the lack benefts. Hand-crafted techniques usually present the performance of interleaving opportunity. It would be desirable to allow batching upper bound; CoroBase strikes a balance between performance, operations across transactions, i.e., inter-transaction batching. programmability and backward compatibility. Second, prior work provided only piece-wise solutions, focusing on optimizing individual database operations (e.g., index traver- 1.3 Contributions and Paper Organization sal [21] and hash join [5, 44]). Despite the signifcant improvement We make four contributions. 1 We highlight the challenges for × (e.g., up to 3 faster for tree probing [21]), it was not clear how much adopting software prefetching in main-memory database engines. overall improvement one can expect when these techniques are 2 We propose a new execution model, coroutine-to-transaction, applied in a full database engine that involves various components. to enable inter-transaction batching and avoid interface changes Overall, these issues lead to two key questions: while retaining the benefts of prefetching. 3 We build CoroBase, a • How should a database engine adopt coroutine-based software main-memory multi-version database engine that uses coroutine-to- prefetching, preferably without requiring application changes? transaction to hide data stalls during index and version chain traver- • How much end-to-end beneft can software prefetching bring to sals. We explore the design tradeofs by describing our experience a database engine under realistic workloads? of transforming an existing engine to use coroutine-to-transaction. 4 We conduct a comprehensive evaluation of CoroBase to quan- 1.2 CoroBase tify the end-to-end efect of prefetching under various workloads. CoroBase is open-source at htps://github.com/sfu-dis/corobase. To answer these questions, we propose and evaluate CoroBase, a Next, we give the necessary background in Section 2. Sections 3– multi-version, main-memory database engine that uses coroutines 4 then present the design principles and details of CoroBase. Sec- to hide data stalls. The crux of CoroBase is a simple but efec- tion 5 quantifes the end-to-end benefts of software prefetching. tive coroutine-to-transaction paradigm that models transactions as We cover related work in Section 6 and conclude in Section 7. coroutines, to enable inter-transaction batching and maintain back- ward compatibility. Worker threads receive transaction requests 2 BACKGROUND and switch among transactions (rather than requests within a trans- action) without requiring intra-transaction batching or multi-key This section gives the necessary background on software prefetch- interfaces. As Figure 1(c) shows, the application remains unchanged ing techniques and coroutines to motivate our work. as batching and interleaving happen at the transaction level. Coroutine-to-transaction can be easily adopted to hide data stalls 2.1 Software Prefetching in diferent database engine components and can even work to- Although modern CPUs use sophisticated hardware prefetching gether with multi-key based approaches. In particular, in multi- mechanisms, they are not efective on reducing pointer-chasing version systems versions of data records are typically chained using overheads, due to the irregular access patterns in pointer-intensive linked lists [62], traversing which constitutes another main source data structures. For instance, when traversing a tree, it is difcult of data stalls, in addition to index traversals. CoroBase transpar- for hardware to predict and prefetch correctly the node which is ently
Load more

Recommended publications
  • The Early History of Smalltalk
    The Early History of Smalltalk http://www.accesscom.com/~darius/EarlyHistoryS... The Early History of Smalltalk Alan C. Kay Apple Computer [email protected]# Permission to copy without fee all or part of this material is granted provided that the copies are not made or distributed for direct commercial advantage, the ACM copyright notice and the title of the publication and its date appear, and notice is given that copying is by permission of the Association for Computing Machinery. To copy otherwise, or to republish, requires a fee and/or specific permission. HOPL-II/4/93/MA, USA © 1993 ACM 0-89791-571-2/93/0004/0069...$1.50 Abstract Most ideas come from previous ideas. The sixties, particularly in the ARPA community, gave rise to a host of notions about "human-computer symbiosis" through interactive time-shared computers, graphics screens and pointing devices. Advanced computer languages were invented to simulate complex systems such as oil refineries and semi-intelligent behavior. The soon-to- follow paradigm shift of modern personal computing, overlapping window interfaces, and object-oriented design came from seeing the work of the sixties as something more than a "better old thing." This is, more than a better way: to do mainframe computing; for end-users to invoke functionality; to make data structures more abstract. Instead the promise of exponential growth in computing/$/volume demanded that the sixties be regarded as "almost a new thing" and to find out what the actual "new things" might be. For example, one would compute with a handheld "Dynabook" in a way that would not be possible on a shared mainframe; millions of potential users meant that the user interface would have to become a learning environment along the lines of Montessori and Bruner; and needs for large scope, reduction in complexity, and end-user literacy would require that data and control structures be done away with in favor of a more biological scheme of protected universal cells interacting only through messages that could mimic any desired behavior.
    [Show full text]
  • Object-Oriented Programming in the Beta Programming Language
    OBJECT-ORIENTED PROGRAMMING IN THE BETA PROGRAMMING LANGUAGE OLE LEHRMANN MADSEN Aarhus University BIRGER MØLLER-PEDERSEN Ericsson Research, Applied Research Center, Oslo KRISTEN NYGAARD University of Oslo Copyright c 1993 by Ole Lehrmann Madsen, Birger Møller-Pedersen, and Kristen Nygaard. All rights reserved. No part of this book may be copied or distributed without the prior written permission of the authors Preface This is a book on object-oriented programming and the BETA programming language. Object-oriented programming originated with the Simula languages developed at the Norwegian Computing Center, Oslo, in the 1960s. The first Simula language, Simula I, was intended for writing simulation programs. Si- mula I was later used as a basis for defining a general purpose programming language, Simula 67. In addition to being a programming language, Simula1 was also designed as a language for describing and communicating about sys- tems in general. Simula has been used by a relatively small community for many years, although it has had a major impact on research in computer sci- ence. The real breakthrough for object-oriented programming came with the development of Smalltalk. Since then, a large number of programming lan- guages based on Simula concepts have appeared. C++ is the language that has had the greatest influence on the use of object-oriented programming in industry. Object-oriented programming has also been the subject of intensive research, resulting in a large number of important contributions. The authors of this book, together with Bent Bruun Kristensen, have been involved in the BETA project since 1975, the aim of which is to develop con- cepts, constructs and tools for programming.
    [Show full text]
  • CPS323 Lecture: Concurrency Materials: 1. Coroutine Projectables
    CPS323 Lecture: Concurrency Materials: 1. Coroutine Projectables 2. Handout for Ada Concurrency + Executable form (simple_tasking.adb, producer_and_consumer.adb) I. Introduction - ------------ A. Most of our attention throughout the CS curricum has been focussed on _sequential_ programming, in which a program does exactly one thing at a time, following a predictable order of steps. In particular, we expect a given program will always follow the exact same sequence of steps when run on a given set of data. B. An alternative is to think in terms of _concurrent_ programming, in which a "program" (at least in principle) does multiple things at the same time, following an order of steps that is not predictable and may differ between runs even if the same program is run on exactly the same data. C. Concurrency has long been an interest in CS, but has become of particular interest as we move into a situation in which raw hardware speeds have basically plateaued and multicore processors are coming to dominate the hardware scene. There are at least three reasons why this topic is of great interest. 1. Achieving maximum performance using technologies such as multicore processors. 2. Systems that inherently require multiple processors working together cooperatively on a single task - e.g. distributed or embedded systems. 3. Some problems are more naturally addressed by thinking in terms of multiple concurrrent components, rather than a single monolithic program. D. There are two broad approaches that might be taken to concurrency: 1. Make use of system libraries, without directly supporting parallelism in the language. (The approach taken by most languages - e.g.
    [Show full text]
  • A Low-Cost Implementation of Coroutines for C
    University of Wollongong Research Online Department of Computing Science Working Faculty of Engineering and Information Paper Series Sciences 1983 A low-cost implementation of coroutines for C Paul A. Bailes University of Wollongong Follow this and additional works at: https://ro.uow.edu.au/compsciwp Recommended Citation Bailes, Paul A., A low-cost implementation of coroutines for C, Department of Computing Science, University of Wollongong, Working Paper 83-9, 1983, 24p. https://ro.uow.edu.au/compsciwp/76 Research Online is the open access institutional repository for the University of Wollongong. For further information contact the UOW Library: [email protected] A LOW-COST IMPLEMENTATION OF COROUTINES FOR C Paul A. Bailes Department of Computing Science University of Wollongong Preprint No. 83-9 November 16, 1983 P.O. Box 1144, WOLLONGONG N.S.W. 2500, AUSTRALIA tel (042)-282-981 telex AA29022 A Low-Cost Implementation of Coroutines for C Paul A. Bailes Department of Computing Science University of Wollongong Wollongong N.S.W. 2500 Australia ABSTRACT We identify a set of primitive operations supporting coroutines, and demonstrate their usefulness. We then address their implementation in C accord­ ing to a set of criteria aimed at maintaining simplicity, and achieve a satisfactory compromise between it and effectiveness. Our package for the PDP-II under UNIXt allows users of coroutines in C programs to gain access to the primitives via an included definitions file and an object library; no penalty is imposed upon non-coroutine users. October 6, 1983 tUNIX is a Trademark of Bell Laboratories. A Low-Cost Implementation of Coroutines for C Paul A.
    [Show full text]
  • Kotlin Coroutines Deep Dive Into Bytecode #Whoami
    Kotlin Coroutines Deep Dive into Bytecode #whoami ● Kotlin compiler engineer @ JetBrains ● Mostly working on JVM back-end ● Responsible for (almost) all bugs in coroutines code Agenda I will talk about ● State machines ● Continuations ● Suspend and resume I won’t talk about ● Structured concurrency and cancellation ● async vs launch vs withContext ● and other library related stuff Agenda I will talk about Beware, there will be code. A lot of code. ● State machines ● Continuations ● Suspend and resume I won’t talk about ● Structured concurrency and cancellation ● async vs launch vs withContext ● and other library related stuff Why coroutines ● No dependency on a particular implementation of Futures or other such rich library; ● Cover equally the "async/await" use case and "generator blocks"; ● Make it possible to utilize Kotlin coroutines as wrappers for different existing asynchronous APIs (such as Java NIO, different implementations of Futures, etc). via coroutines KEEP Getting Lazy With Kotlin Pythagorean Triples fun printPythagoreanTriples() { for (i in 1 until 100) { for (j in 1 until i) { for (k in i until 100) { if (i * i + j * j < k * k) { break } if (i * i + j * j == k * k) { println("$i^2 + $j^2 == $k^2") } } } } } Pythagorean Triples fun printPythagoreanTriples() { for (i in 1 until 100) { for (j in 1 until i) { for (k in i until 100) { if (i * i + j * j < k * k) { break } if (i * i + j * j == k * k) { println("$i^2 + $j^2 == $k^2") } } } } } Pythagorean Triples fun printPythagoreanTriples() { for (i in 1 until 100) { for (j
    [Show full text]
  • Csc 520 Principles of Programming Languages Coroutines Coroutines
    Coroutines Coroutines are supported by Simula and Modula-2. CSc 520 They are similar to Java’s threads, except the programmer has to explicitly transfer control from one Principles of Programming execution context to another. Languages Thus, like threads several coroutines can exist simultaneously but unlike threads there is no central 36: Procedures — Coroutines scheduler that decides which coroutine should run next. Christian Collberg A coroutine is represented by a closure. [email protected] A special operation transfer(C) shifts control to the coroutine C, at the location where C last left off. Department of Computer Science University of Arizona Copyright c 2005 Christian Collberg 520—Spring 2005—36 [1] 520—Spring 2005—36 [2] Coroutines. Coroutines. The next slide shows an example from Scott where two var us, cfs: coroutine; coroutines execute “concurrently”, by explicitly transferring control between each other. coroutine update_screen() { ... In the example one coroutine displays a moving detach screen-saver, the other walks the file-system to check loop { for corrupt files. ... transfer(cfs) ... } } coroutine check_file_system() { ... } main () { ... } 520—Spring 2005—36 [3] 520—Spring 2005—36 [4] Coroutines. Coroutines in Modula-2 coroutine check_file_system() { Modula-2's system module provides two functions to create and transfer ... between coroutines: detach for all files do { PROCEDURE NEWPROCESS( proc: PROC; (* The procedure *) ... transfer(cfs) addr: ADDRESS; (* The stack *) ... transfer(cfs) size: CARDINAL; (* The stack size *) ... transfer(cfs) ... VAR new: ADDRESS); (* The coroutine *) } PROCEDURE TRANSFER( } VAR source: ADDRESS; (* Current coroutine *) VAR destination: ADDRESS); (* New coroutine *) main () { us := new update_screen(); The ®rst time TRANSFER is called source will be instantiated to cfs := new check_file_system(); the main (outermost) coroutine.
    [Show full text]
  • Practical Perl Tools Parallel Asynchronicity, Part 2
    COLUMNS Practical Perl Tools Parallel Asynchronicity, Part 2 DAVID N. BLANK-EDELMAN David Blank-Edelman is elcome back for Part 2 of this mini-series on modern methods the Technical Evangelist at for doing multiple things at once in Perl. In the first part (which I Apcera (the comments/ highly recommend that you read first before reading this sequel), views here are David’s alone W and do not represent Apcera/ we talked about some of the simpler methods for multi-tasking like the use Ericsson) . He has spent close to thirty years of fork() and Parallel::ForkManager. We had just begun to explore using the in the systems administration/DevOps/SRE Coro module as the basis for using threads in Perl (since the native stuff is so field in large multiplatform environments ucky) when we ran out of time. Let’s pick up the story roughly where we left it. including Brandeis University, Cambridge Technology Group, MIT Media Laboratory, Coro and Northeastern University. He is the author As a quick reminder, Coro offers an implementation of coroutines that we are going to use as of the O’Reilly Otter book Automating System just a pleasant implementation of cooperative threading (see the previous column for more Administration with Perl and is a frequent invited picayune details around the definition of a coroutine). By cooperative, we mean that each speaker/organizer for conferences in the field. thread gets queued up to run, but can only do so after another thread has explicitly signaled David is honored to serve on the USENIX that it is ready to cede its time in the interpreter.
    [Show full text]
  • Coroutines and Generators Chapter Three
    Coroutines and Generators Coroutines and Generators Chapter Three 3.1 Chapter Overview This chapter discusses two special types of program units known as coroutines and generators. A coroutine is similar to a procedure and a generator is similar to a function. The principle difference between these program units and procedures/functions is that the call/return mechanism is different. Coroutines are especially useful for multiplayer games and other program flow where sections of code "take turns" execut- ing. Generators, as their name implies, are useful for generating a sequence of values; in many respects generators are quite similar to HLA’s iterators without all the restrictions of the iterators (i.e., you can only use iterators within a FOREACH loop). 3.2 Coroutines A common programming paradigm is for two sections of code to swap control of the CPU back and forth while executing. There are two ways to achieve this: preemptive and cooperative. In a preemptive sys- tem, two or more processes or threads take turns executing with the task switch occurring independently of the executing code. A later volume in this text will consider preemptive multitasking, where the Operating System takes responsibility for interrupting one task and transferring control to some other task. In this chapter we’ll take a look at coroutines that explicitly transfer control to another section of the code1 When discussing coroutines, it is instructive to review how HLA’s iterators work, since there is a strong correspondence between iterators and coroutines. Like iterators, there are four types of entries and returns associated with a coroutine: • Initial entry.
    [Show full text]
  • Deriving Type Systems and Implementations for Coroutines
    Deriving Type Systems and Implementations for Coroutines Konrad Anton and Peter Thiemann Institut f¨urInformatik, Universit¨atFreiburg {anton,thiemann}@informatik.uni-freiburg.de Abstract. Starting from reduction semantics for several styles of corou- tines from the literature, we apply Danvy’s method to obtain equivalent functional implementations (definitional interpreters) for them. By ap- plying existing type systems for programs with continuations, we obtain sound type systems for coroutines through the translation. The resulting type systems are similar to earlier hand-crafted ones. As a side product, we obtain implementations for these styles of coroutines in OCaml. 1 Introduction Coroutines are an old programming construct, dating back to the 1960s [5]. They have been neglected for a while, but are currently enjoying a renaissance (e.g. in Lua [12]), sometimes in the limited form of generators (Python [20], C# [17]) and sometimes under different names (e.g., fibers in .NET). Type systems for coroutines have not been considered in the past. Coroutines without parameters and return values (Simula, Modula 2 [21]), coroutine opera- tions whose effects are tied to the static structure of the program (ACL, [16]), or coroutines lexically limited to the body of one function (C#), could be integrated into said languages without special support in the type system. In an earlier paper [1], we developed the first type system for a simply-typed λ-calculus with coroutines. This development was done in an ad-hoc style for a feature-rich calculus and resulted in a type and effect system with a simple notion of subeffecting to capture the control effects of coroutine operations.
    [Show full text]
  • CS164: Introduction to Programming Languages and Compilers, Spring 2012 Thibaud Hottelier UC Berkeley
    Lecture 5 Implementing Coroutines compile AST to bytecode, bytecode interpreter Ras Bodik Hack Your Language! Shaon Barman CS164: Introduction to Programming Thibaud Hottelier Languages and Compilers, Spring 2012 UC Berkeley 1 What you will learn today Implement Asymmetric Coroutines – why a recursive interpreter with implicit stack won’t do Compiling AST to bytecode - this is your first compiler; compiles AST to “flat” code Bytecode Interpreter - bytecode can be interpreted without recursion - hence no need to keep interpreter state on the call stack 2 PA2 PA2 was released today, due Sunday – bytecode interpreter of coroutines – after PA2, you will be able to implement iterators – in PA3, you will build Prolog on top of your coroutines – extra credit: cool use of coroutines (see L4 reading) HW3 has been assigned: cool uses of coroutines This homework is not graded. While it is optional, you are expected to know the homework material: 1) lazy list concatenation 2) regexes Solve at least the lazy list problem before you start on PA2 3 Code 4 Cal Hackathon Friday, February 3, 9:00pm to Saturday, February 4 5:00pm Soda Hall Wozniak Lounge Grand Prize: $1,500!!! Register @ http://code4cal.eventbrite.com/ More information about the event at http://stc.berkeley.edu. The Student Technology Council (STC), an advisory council for the UC Berkeley CIO, Shel Waggener, is hosting Code 4 Cal, a hackathon for students to create innovative, sustainable, and most of all, useful applications or widgets for Cal students. Student-developed app could be adopted by the University! Cash prizes start at $1,500. 4 Review of L4: Why Coroutines Loop calls iterator function to get the next item eg the next token from the input The iterator maintains state between two such calls eg pointer to the input stream.
    [Show full text]
  • Specialising Dynamic Techniques for Implementing the Ruby Programming Language
    SPECIALISING DYNAMIC TECHNIQUES FOR IMPLEMENTING THE RUBY PROGRAMMING LANGUAGE A thesis submitted to the University of Manchester for the degree of Doctor of Philosophy in the Faculty of Engineering and Physical Sciences 2015 By Chris Seaton School of Computer Science This published copy of the thesis contains a couple of minor typographical corrections from the version deposited in the University of Manchester Library. [email protected] chrisseaton.com/phd 2 Contents List of Listings7 List of Tables9 List of Figures 11 Abstract 15 Declaration 17 Copyright 19 Acknowledgements 21 1 Introduction 23 1.1 Dynamic Programming Languages.................. 23 1.2 Idiomatic Ruby............................ 25 1.3 Research Questions.......................... 27 1.4 Implementation Work......................... 27 1.5 Contributions............................. 28 1.6 Publications.............................. 29 1.7 Thesis Structure............................ 31 2 Characteristics of Dynamic Languages 35 2.1 Ruby.................................. 35 2.2 Ruby on Rails............................. 36 2.3 Case Study: Idiomatic Ruby..................... 37 2.4 Summary............................... 49 3 3 Implementation of Dynamic Languages 51 3.1 Foundational Techniques....................... 51 3.2 Applied Techniques.......................... 59 3.3 Implementations of Ruby....................... 65 3.4 Parallelism and Concurrency..................... 72 3.5 Summary............................... 73 4 Evaluation Methodology 75 4.1 Evaluation Philosophy
    [Show full text]
  • Language Design and Implementation Using Ruby and the Interpreter Pattern
    Language Design and Implementation using Ruby and the Interpreter Pattern Ariel Ortiz Information Technology Department Tecnológico de Monterrey, Campus Estado de México Atizapán de Zaragoza, Estado de México, Mexico. 52926 [email protected] ABSTRACT to explore different language concepts and programming styles. In this paper, the S-expression Interpreter Framework (SIF) is Section 4 describes briefly how the SIF has been used in class. presented as a tool for teaching language design and The conclusions are found in section 5. implementation. The SIF is based on the interpreter design pattern and is written in the Ruby programming language. Its core is quite 1.1 S-Expressions S-expressions (symbolic expressions) are a parenthesized prefix small, but it can be easily extended by adding primitive notation, mainly used in the Lisp family languages. They were procedures and special forms. The SIF can be used to demonstrate selected as the framework’s source language notation because advanced language concepts (variable scopes, continuations, etc.) they offer important advantages: as well as different programming styles (functional, imperative, and object oriented). • Both code and data can be easily represented. Adding a new language construct is pretty straightforward. • Categories and Subject Descriptors The number of program elements is minimal, thus a parser is − relatively easy to write. D.3.4 [Programming Languages]: Processors interpreters, • run-time environments. The arity of operators doesn’t need to be fixed, so, for example, the + operator can be defined to accept any number of arguments. General Terms • There are no problems regarding operator precedence or Design, Languages. associativity, because every operator has its own pair of parentheses.
    [Show full text]