A Performance Study of Protocols Used in a Print on Demand Server

Total Page:16

File Type:pdf, Size:1020Kb

A Performance Study of Protocols Used in a Print on Demand Server A performance study of protocols used in a print on demand server SAM SAM Master’s Thesis at ICT Examiner: Fredrik Kilander Supervisor: Fredrik Kilander Industrial supervisor: Joe Armstrong TRITA-ICT-EX-2015:16 iii Abstract A performance evaluation of different protocols, both textual and binary based, is done by implementing a simple print-on-demand service as the test bench. The measurements are done with respect to the serialization method, a method defining the procedure to encode structured data to a stream of bytes. The result of this evaluation may play a key in forming a decision regarding which protocol to utilize for mobile networks or networks with high demand. The evaluated protocols are Protocol Buffers, BERT, ASN.1, JSON, and XML. The result shows that Protocol Buffers had best performance for most of the tests and that XML had worst performance for all tests. iv Sammanfattning En prestandautvärdering av olika protokoll, både text och binärbaserade, har gjorts genom att implementera en enkel print-on-demand service som testbänk. Mätningarna är gjorda med avseende på serialiseringsmetoden, en metod som definerar tillvägagångsättet att koda strukturerad data till en ström av bytes. Resultatet av denna evaluering kan spela en roll i bestämmandet av vilken protokoll att använda för mobila nätverk eller nätverk med hög efterfrågan. De evaluerade protokollen är Protocol Buffers, BERT, ASN.1, JSON och XML. Resultatet visar att Protocol Buffers presterade bäst för de flesta testen och XML presterade sämst för alla test. Contents Contents v 1 Introduction 1 1.1 Motivation . 1 1.2 Problem Statement . 2 1.3 Scope . 2 1.4 Purpose . 3 1.5 Sustainable development . 3 1.6 Methodology . 3 1.7 Thesis outline . 3 2 Background 5 2.1 Related work . 5 2.2 Environment . 7 2.2.1 Erlang . 7 2.2.2 0MQ . 9 2.2.3 LibHaru . 10 2.2.4 ZLib . 10 2.3 Protocol Description Languages . 11 2.3.1 Protocol Buffers . 12 2.3.2 BERT . 14 2.3.3 ASN.1 . 15 2.3.4 JSON . 17 2.3.5 XML . 18 3 Methodology 21 3.1 Literature study . 21 3.2 Implementation . 23 3.3 Measurements and analysis . 24 4 Implementation overview 27 4.1 The 0MQ connection . 28 4.2 The client . 28 4.3 The server . 28 v vi CONTENTS 5 Code generation 31 5.1 Overview . 31 5.2 LibHaru API documentation . 31 5.3 Structured API specification . 32 5.4 Generated code . 33 5.4.1 Port code generation . 34 5.4.2 Erlang module template . 36 5.4.3 Protocol buffers code generation . 36 5.4.4 Bert code generation . 37 5.4.5 ASN.1 code generation . 38 5.4.6 JSON code generation . 39 5.4.7 XML code generation . 40 6 Test and measurement programs 41 6.1 Overview . 41 6.2 Measurements on the client side . 42 6.3 Measurements on the server side . 43 6.4 Test data sets . 43 7 Analysis tools 45 7.1 Overview . 45 7.2 From data to charts . 46 8 Empirical evaluation 49 8.1 Test design . 49 8.2 Test implementation and setup . 49 8.3 Test results and analysis . 51 8.3.1 Encoding performance . 51 8.3.2 Decoding performance . 54 8.3.3 Size . 56 8.3.4 Round trip time . 58 8.3.5 Overall Performance . 60 8.3.6 Speed and size performance . 62 9 Conclusions 65 9.1 Summary . 65 9.2 Conclusion . 65 9.3 Discussion . 66 9.4 Future Work . 67 References 69 A All test results 73 A.1 Encoding performance . 73 A.2 Decoding performance . 75 CONTENTS vii A.3 Size . 77 A.4 Round trip time . 79 A.5 Overall Performance . 81 A.6 Speed and size performance . 83 Chapter 1 Introduction This chapter introduces the reader to the thesis and presents the motivation. This work investigates the performance of a network service by sending data (or messages) between a client and a server and measure how the performance varies in respect to changes of the serialization mechanism (used to pack the messages) and the size of the messages. Messages, have specific data, structured according to a specification with predefined syntactic rules. The result of this evaluation may play a key in forming a decision regarding which protocol to utilize for which specific purpose. For instance, to determine which of the evaluated protocols in this study are most fit for mobile networks or networks under load. The protocols that have been evaluated are Protocol Buffers, BERT, ASN.1, JSON and XML. For evalua- tion of the different protocols, a simple print-on-demand service is implemented for the various protocols. A measurement of performance is made and the results are evaluated. The network service in this case creates PDF-files from messages sent from a client over a network. The service has two parts, a server and a client, where the former receives messages from network sockets and creates PDF-files, and the latter is the application that sends messages of what to include in the PDF-files. We measure the time to encode and decode messages as well as message density, and also the throughput of the system measured in PDF pages per second. 1.1 Motivation In wireless communication, the bandwidth is limited. An example of this is LTE 4G (Long-term evolution fourth generation), a standard for wireless communication of high-speed data for mobile phones and data terminals. An LTE 4G cell have a limited capacity of active users with a peak of 300MB/s [20]. This means that a user connected to such a network have a theoretical download speed of 300MB/s, however if several users are sharing this bandwidth the speed per user would de- 1 2 CHAPTER 1. INTRODUCTION crease. Another important aspect to consider is that most mobile network operators sell limited data plans. It is therefore important, when using a wireless network, to be frugal with what you send. In many wired services it is instead more important to package messages quickly than to send small packets. An example of this is a bank where the load is high with many transactions being made in a short time. Given the motivations above, which protocol to use is important. Thus the project providers at Ericsson proposed to evaluate protocol description languages for a PDF-generator as a simple practical implementation of this problem. 1.2 Problem Statement This thesis evaluates packet size and packaging speed of various combinations of protocols and data set types sent over a network. This is to determine the different optimal combinations and answer the following questions for the protocols Protocol Buffer, BERT, ASN.1 JSON and XML: • Which of the packaging mechanisms are the fastest regardless of data set? • Which of the packaging mechanisms produce the smallest packet size regard- less of data set? The protocols are used to send messages locally in one computer with and without compression for further evaluation of the protocols compactness. A print on demand service is the test bench and the following performance metrics are studied: • The number of PDF pages created per second • The round-trip time of sending a message and receiving an acknowledgment • The time to serialize a message • The time to deserialize a message • The size of a message 1.3 Scope Given there are many protocols, this thesis focuses on 5 protocols as representatives of most protocols. The measurements that are made focuses on the method of when a message is encoded/decoded and the relation between number of bytes and the actual content of the message. As this thesis is interested in the different serialization mechanisms, it is not relevant to send the messages in a parallel system. Meaning, every next message will only be sent when an acknowledgment is received from the server. 1.4. PURPOSE 3 1.4 Purpose The purpose of this performance study is to answer the questions presented in sec- tion 1.2 by evaluating a variety of protocols. The author of this thesis hopes of giving a good understanding to the reader of the difference between packaging mechanisms in a practical sense. The author would also like to convey the importance of choos- ing the right protocol when developing a service with a limited network or when using a network with great load. 1.5 Sustainable development The effect of a performance study on protocols could be in many ways beneficial for sustainable development. From an economical aspect, it will most likely be to an advantage for mobile network users to use services with minimal data transfer. It is also ecologically beneficial to apply protocols that use less CPU-power and smaller packets as these two factors have great impact on battery usage. Of course, this does not only apply to mobile phones. The internet of things(IoT) has extended the usage of mobile networks tremendously over the years. Using a more compact and faster protocol for internet devices can have a great influence on both economical and ecological aspects. And naturally, the cheaper the usage of a device becomes, the more people can use it. 1.6 Methodology A short investigation of different tools and libraries was made. After defining what libraries to use, a print on demand service was implemented together with a spe- cific protocol to create the test bench. The purpose of the experiment is to un- derstand how the protocols perform in a practical sense and the purpose of the PDF-generating service is to have a test bench that can handle a wide variety of data types.
Recommended publications
  • Release 0.11 Todd Gamblin
    Spack Documentation Release 0.11 Todd Gamblin Feb 07, 2018 Basics 1 Feature Overview 3 1.1 Simple package installation.......................................3 1.2 Custom versions & configurations....................................3 1.3 Customize dependencies.........................................4 1.4 Non-destructive installs.........................................4 1.5 Packages can peacefully coexist.....................................4 1.6 Creating packages is easy........................................4 2 Getting Started 7 2.1 Prerequisites...............................................7 2.2 Installation................................................7 2.3 Compiler configuration..........................................9 2.4 Vendor-Specific Compiler Configuration................................ 13 2.5 System Packages............................................. 16 2.6 Utilities Configuration.......................................... 18 2.7 GPG Signing............................................... 20 2.8 Spack on Cray.............................................. 21 3 Basic Usage 25 3.1 Listing available packages........................................ 25 3.2 Installing and uninstalling........................................ 42 3.3 Seeing installed packages........................................ 44 3.4 Specs & dependencies.......................................... 46 3.5 Virtual dependencies........................................... 50 3.6 Extensions & Python support...................................... 53 3.7 Filesystem requirements........................................
    [Show full text]
  • Documentation of the Plplot Plotting Software I
    Documentation of the PLplot plotting software i Documentation of the PLplot plotting software Documentation of the PLplot plotting software ii Copyright © 1994 Maurice J. LeBrun, Geoffrey Furnish Copyright © 2000-2005 Rafael Laboissière Copyright © 2000-2016 Alan W. Irwin Copyright © 2001-2003 Joao Cardoso Copyright © 2004 Andrew Roach Copyright © 2004-2013 Andrew Ross Copyright © 2004-2016 Arjen Markus Copyright © 2005 Thomas J. Duck Copyright © 2005-2010 Hazen Babcock Copyright © 2008 Werner Smekal Copyright © 2008-2016 Jerry Bauck Copyright © 2009-2014 Hezekiah M. Carty Copyright © 2014-2015 Phil Rosenberg Copyright © 2015 Jim Dishaw Redistribution and use in source (XML DocBook) and “compiled” forms (HTML, PDF, PostScript, DVI, TeXinfo and so forth) with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code (XML DocBook) must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified. 2. Redistributions in compiled form (transformed to other DTDs, converted to HTML, PDF, PostScript, and other formats) must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Important: THIS DOCUMENTATION IS PROVIDED BY THE PLPLOT PROJECT “AS IS” AND ANY EXPRESS OR IM- PLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PLPLOT PROJECT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    [Show full text]
  • Documentation of the Plplot Plotting Software I
    Documentation of the PLplot plotting software i Documentation of the PLplot plotting software Documentation of the PLplot plotting software ii Copyright © 1994 Maurice J. LeBrun, Geoffrey Furnish Copyright © 2000-2005 Rafael Laboissière Copyright © 2000-2016 Alan W. Irwin Copyright © 2001-2003 Joao Cardoso Copyright © 2004 Andrew Roach Copyright © 2004-2013 Andrew Ross Copyright © 2004-2016 Arjen Markus Copyright © 2005 Thomas J. Duck Copyright © 2005-2010 Hazen Babcock Copyright © 2008 Werner Smekal Copyright © 2008-2016 Jerry Bauck Copyright © 2009-2014 Hezekiah M. Carty Copyright © 2014-2015 Phil Rosenberg Copyright © 2015 Jim Dishaw Redistribution and use in source (XML DocBook) and “compiled” forms (HTML, PDF, PostScript, DVI, TeXinfo and so forth) with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code (XML DocBook) must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified. 2. Redistributions in compiled form (transformed to other DTDs, converted to HTML, PDF, PostScript, and other formats) must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. Important: THIS DOCUMENTATION IS PROVIDED BY THE PLPLOT PROJECT “AS IS” AND ANY EXPRESS OR IM- PLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE PLPLOT PROJECT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
    [Show full text]
  • Expert Curriculum Vitae
    Expert Curriculum Vitae Photo Name Alexander Wittrock Address Eimsbütteler Chaussee 85 D-20259 Hamburg Date of birth 1975-03-14 Nationality German Education 1998 - Apprenticeship as management assistant in data processing 1994 - European Business Baccalaureate Diploma Languages German, English, French Phone +49 (0) 162 438 438 7 E-mail [email protected] Web www.brainlessdesigns.de Work experience Duration: March 2020 – Today Company: software & vision Sarrazin GmbH & Co. KG Marktallee 3 D-48165 Münster, Germany Position: Software Developer Project description: Developed a cross platform software solution for a customer in Hamburg in the eyewear industry Standards / Tools: C / C++/C#, Qt 5.6, Python, PostgreSQL 14, Visual Studio 2017, Windows 10, Ubuntu Linux, Tortoise Git, Jira, libreOffice, MS Teams, TeamViewer 13, Notepad++ Duration: March 2019 – September 2019 Company: M+F Technologies GmbH Helbingtwiete 5 D-22047 Hamburg, Germany Position: Software Developer Project description: Developed drivers for different hardware devices and partly refactored a software for the oil industry by using new developed libraries and unit tests Standards / Tools: C / C++, Python, Visual Studio 2017, Windows 10, Tortoise SVN, Jira, Office 2017, TeamViewer 13, Notepad++ Duration: September 2018 – February 2019 Company: Domino Laser GmbH Fangdieckstr. 75a D-22547 Hamburg, Germany Position: Software Developer Project description: Developed a frontend, backend and unit tests for laser printer products Standards / Tools: C / C++, Qt, Windows 10, Ubuntu
    [Show full text]
  • 9 Bringing Java's Wild Native World Under Control
    TISSEC1603-09 ACM-TRANSACTION November 15, 2013 12:4 9 Bringing Java’s Wild Native World under Control MENGTAO SUN, GANG TAN, JOSEPH SIEFERS, and BIN ZENG, Lehigh University GREG MORRISETT,HarvardUniversity For performance and for incorporating legacy libraries, many Java applications contain native-code com- ponents written in unsafe languages such as C and C++. Native-code components interoperate with Java components through the Java Native Interface (JNI). As native code is not regulated by Java’s security model, it poses serious security threats to the managed Java world. We introduce a security framework that extends Java’s security model and brings native code under control. Leveraging software-based fault isolation, the framework puts native code in a separate sandbox and allows the interaction between the native world and the Java world only through a carefully designed pathway. Two different implementa- tions were built. In one implementation, the security framework is integrated into a Java Virtual Machine (JVM). In the second implementation, the framework is built outside of the JVM and takes advantage of JVM-independent interfaces. The second implementation provides JVM portability, at the expense of some performance degradation. Evaluation of our framework demonstrates that it incurs modest runtime overhead while significantly enhancing the security of Java applications. Categories and Subject Descriptors: D.4.6 [Software]: Operating Systems—Security and protection; D.2.12 [Software]: Software Engineering—Interoperability General Terms: Security Additional Key Words and Phrases: Java native interface, Java virtual machine, software-based fault isolation ACM Reference Format: Sun, M., Tan, G., Siefers, J., Zeng, B., and Morrisett, G.
    [Show full text]
  • Easybuild Documentation Release 20150714.01
    EasyBuild Documentation Release 20150714.01 Ghent University Tue, 14 Jul 2015 12:47:12 Contents 1 Introductory topics 3 1.1 What is EasyBuild?.........................................3 1.2 Concepts and terminology......................................4 1.3 Typical workflow example: building and installing WRF......................6 2 Getting started 9 2.1 Installing EasyBuild.........................................9 2.2 Configuring EasyBuild........................................ 16 3 Basic usage topics 27 3.1 Using the EasyBuild command line................................. 27 3.2 Writing easyconfig files: the basics................................. 36 3.3 Understanding EasyBuild logs.................................... 42 4 Advanced usage topics 45 4.1 Experimental features........................................ 45 4.2 Including additional Python modules (--include-*)...................... 45 4.3 Integration with GitHub....................................... 47 4.4 Manipulating dependencies..................................... 49 4.5 Packaging support.......................................... 50 4.6 Partial installations.......................................... 53 4.7 Submitting jobs using --job .................................... 57 4.8 Using external modules....................................... 63 5 Other topics 65 5.1 Code style.............................................. 65 5.2 Unit tests............................................... 65 5.3 Useful scripts............................................. 69 5.4 Deprecated functionality......................................
    [Show full text]
  • PHP 7 Und Mysql – Das Umfassende Handbuch 1.039 Seiten, Gebunden, 2
    Wissen, wie’s geht. Leseprobe Erfahren Sie alles über PHP und moderne Datenbankentwicklung. In dieser Leseprobe lernen Sie die Programmiergrundlagen von PHP und den wichtigen Einsatz von Strings kennen. Außerdem erhalten Sie das vollständige Inhalts- und Stichwortverzeichnis des Buches. »Grundlagen der Sprache« »Programmieren« »Strings« Inhaltsverzeichnis Index Die Autoren Leseprobe weiterempfehlen Christian Wenz, Tobias Hauser PHP 7 und MySQL – Das umfassende Handbuch 1.039 Seiten, gebunden, 2. Auflage 2016 44,90 Euro, ISBN 978-3-8362-4082-6 www.rheinwerk-verlag.de/4090 4082.book Seite 95 Donnerstag, 7. April 2016 3:44 15 Kapitel 4 4 Grundlagen der Sprache 4 Dieses Kapitel beginnt mit der Syntax von PHP und zeigt Ihnen, wie Sie mit PHP programmieren. Für fortgeschrittene Leser bildet es ein gutes Nachschlagewerk, wenn einzelne Konstrukte unklar sind. PHP ist nicht schwer zu erlernen. Dieses Versprechen steht am Anfang einer umfang- reichen Spracheinführung, die alle wesentlichen Aspekte der Sprache beleuchten wird. Sie finden viele kleine, einfache Codestücke. Dadurch wird es möglich, dass Sie auch später schnell einzelne Fakten nachschlagen und so immer tiefer in PHP ein- steigen. Tipp Sollten Sie es eilig haben und seltenere Details nicht benötigen, sondern schnell und kompakt die Sprache lernen wollen, lassen Sie beim ersten Lesen einfach Überschrif- ten der vierten Ebene weg. Dort finden Sie meist Hintergrundinformationen zu ein- zelnen Themen, die aber erst im Einzelfall wirklich wichtig werden. 4.1 PHP in HTML Eine Reise in die Tiefen und Untiefen von PHP beginnt bei HTML. PHP wurde als ser- verseitige Programmiersprache konzipiert, die eng in HTML integriert ist. Dies steht im Gegensatz zum Ziel anderer Programmiersprachen, Code und Inhalt zu trennen.
    [Show full text]
  • Polybios 1.3 Making History in PDF
    Polybios 1.3 Making History In PDF Andreas Falkenhahn i Table of Contents 1 General information::::::::::::::::::::::::::::: 1 1.1 Introduction :::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.2 Terms and conditions ::::::::::::::::::::::::::::::::::::::::::: 1 1.3 Requirements::::::::::::::::::::::::::::::::::::::::::::::::::: 2 1.4 Installation ::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 2 About Polybios :::::::::::::::::::::::::::::::::: 5 2.1 Credits ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 5 2.2 Frequently asked questions:::::::::::::::::::::::::::::::::::::: 5 2.3 Future:::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 6 2.4 History ::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 6 3 Viewing PDFs ::::::::::::::::::::::::::::::::::: 7 3.1 Overview ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 7 3.2 Loading pages as vector brushes :::::::::::::::::::::::::::::::: 7 3.3 Loading PDFs as anims::::::::::::::::::::::::::::::::::::::::: 8 4 Creating PDFs :::::::::::::::::::::::::::::::::: 9 4.1 Coordinate system:::::::::::::::::::::::::::::::::::::::::::::: 9 4.2 Graphics mode ::::::::::::::::::::::::::::::::::::::::::::::::: 9 4.3 Painting paths::::::::::::::::::::::::::::::::::::::::::::::::: 10 4.4 Painting text :::::::::::::::::::::::::::::::::::::::::::::::::: 11 4.5 Colors::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 12 4.6 Font types::::::::::::::::::::::::::::::::::::::::::::::::::::: 12 4.7 Base14 fonts:::::::::::::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Text++ Final Report
    text++ Final Report Joi Anderson - jna2123 // Manager + Tester ​ Klarizsa Padilla - ksp2127 // Language Guru + Tester ​ Maria Javier - mj2729 // System Architect + Tester ​ 1 Contents Contents 2 1. Introduction 4 2. Language Tutorial 5 2.1 Environment Setup 5 2.3 Environment Setup 6 3. Language Manual 7 1. Introduction 7 1.1 Software Used 7 The bulk of our code is written in OCaml and compiles to LLVM. We also have a file written in C to make use of the external library LibHaru, which is used in our display/PDF functions. The open source library for generating PDF files (libHaru) is run through a shell script that calls our code and the LLVM interpreter. (We also used the LLVM interpreter frequently when testing individual cases.) To compile to rendering mode, we use the run.sh shell script, which in turn calls a tpp source program. We used github for version control and for the repository. Each team member pulled code to their own computer or virtual machine and used their own choice of IDE. 7 1.2 LibHaru Overview 7 libHaru is a free, cross platform, open source library for generating PDF files. text++ utilizes the following features of LibHaru: 7 Generating PDF files with lines and text. 7 Text placement via a coordinate system. 7 Embedding Type1 font and TrueType font. 7 libHaru is written in ANSI C, so theoretically it supports most of the modern operating systems. 7 2. Lexical Conventions 8 2.1 Comments 8 2.2 Identifiers 8 2.3 Keywords 8 2.3.1 Type-specifiers 9 2.4 Data Types 9 2.4.1 Integer 9 2.4.2 Float 9 2 2.4.3 String 9 2.5 Operators (Overview) 9 2.6 Separators 9 3.1 Function Declarations 10 3.2 Variable Declarations 10 4.
    [Show full text]
  • Easybuild: Building Software with Ease
    EasyBuild: building software with ease Kenneth Hoste HPC-UGent, Ghent University, Belgium [email protected] http://users.ugent.be/~kehoste/EasyBuild-intro-Espoo_20150506.pdf User Support Workshop @ NeIC 2015 (Espoo, Finland) 20150506 http://hpcugent.github.io/easybuild - http://easybuild.readthedocs.org 1/31 HPC-UGent in a nutshell http://www.ugent.be/hpc • HPC team at central IT dept. of Ghent University (Belgium) • 9 team members: 1 manager, ∼3 user support, ∼5 sysadmin • 6(+2) Tier2 clusters + one Tier1 (8.5k cores), >1k servers in total • ∼1.5k user accounts, across all scientific domains • tasks: hardware, system administration, user support/training, . • member of Flemish Supercomputer Centre (VSC) virtual centre, collaboration between Flemish university associations http://hpcugent.github.io/easybuild - http://easybuild.readthedocs.org 2/31 \Please install this on the HPC?" In the context of high performance computing, building from source should be preferred, when possible (i.e., if sources are available). This allows for controlling used compilers and libraries, optimizing the software for the specific system architecture (e.g., AVX, network), etc. Installing (lots of) scientific software is typically: • error-prone, trial-and-error • tedious, hard to get right • repetitive & boring (well. ) • time-consuming (hours, days, even weeks) • frustrating (\Pandora's box") • sometimes simply not worth the effort. http://hpcugent.github.io/easybuild - http://easybuild.readthedocs.org 3/31 Common issues with scientific software Researchers focus on the science behind the software they implement, and care little about tools, build procedure, portability, . Scientists are not software developers or sysadmins (nor should they be). \If we would know what we are doing, it wouldn't be called `research'." This results in: • use of non-standard build tools (or broken ones) • incomplete build procedure, e.g., no configure or install step • interactive installation scripts • hardcoded parameters (compilers, libraries, paths, .
    [Show full text]
  • Computadoras Electronicas
    COMPUTADORAS ELECTRONICAS Prólogo En la unidad 0 se hace una introducción, definiendo algunos conceptos previos. En la unidad 1 se muestran las diversas tecnologías en las que se fueron construyendo las computadoras. Luego se hace una breve revisión de los principios de circuitos digitales secuenciales y combinacionales, para comprender luego el Hardware principal de la computadora, como ser la Unidad Lógico Aritmética y la Unidad De Memoria. También se exponen las principales tecnologías de semiconductor con las que son construidas las computadoras actuales. Y se hace una descripción funcional de todas y cada una de las partes elementales de la computadora. Finalmente se describen los dos tipos básicos de arquitectura de computadoras ejemplificando cada uno. En la unidad 2 se hace un repaso de sistemas posicionales de numeración haciendo especial énfasis en el hexadecimal y binario. Además se desarrollan los diferentes códigos binarios con los que la maquina almacena y procesa la diversa información digital. En la unidad 3 se hace una integración de las unidades anteriores en la programación de un microcontrolador específico. Haciendo uso de un entorno de desarrollo integrado para tal fin. Utilizando el lenguaje Ensamblador ya que al ser de bajo nivel se puede tener una compresión mas profunda de lo que ocurre a nivel Hardware y poder relacionarlo con el Software. En la unidad 4 finalmente se expone el lenguaje C, luego de haber pasado por el Ensamblador se busca un mayor nivel de abstracción para poder resolver problemas de mayor complejidad. Este material se realizó con fines didácticos y se encuentra en proceso de desarrollo.
    [Show full text]
  • ROSE Compiler Framework
    ROSE Compiler Framework Wikibooks.org March 17, 2013 On the 28th of April 2012 the contents of the English as well as German Wikibooks and Wikipedia projects were licensed under Creative Commons Attribution-ShareAlike 3.0 Unported license. An URI to this license is given in the list of figures on page 213. If this document is a derived work from the contents of one of these projects and the content was still licensed by the project under this license at the time of derivation this document has to be licensed under the same, a similar or a compatible license, as stated in section 4b of the license. The list of contributors is included in chapter Contributors on page 211. The licenses GPL, LGPL and GFDL are included in chapter Licenses on page 217, since this book and/or parts of it may or may not be licensed under one or more of these licenses, and thus require inclusion of these licenses. The licenses of the figures are given in the list of figures on page 213. This PDF was generated by the LATEX typesetting software. The LATEX source code is included as an attachment (source.7z.txt) in this PDF file. To extract the source from the PDF file, we recommend the use of http://www.pdflabs.com/tools/pdftk-the-pdf-toolkit/ utility or clicking the paper clip attachment symbol on the lower left of your PDF Viewer, selecting Save Attachment. After extracting it from the PDF file you have to rename it to source.7z. To uncompress the resulting archive we recommend the use of http://www.7-zip.org/.
    [Show full text]