Energy efficiency across programming languages: How do energy, time, and memory relate?

Rui Pereira, Marco Couto, Francisco Ribeiro, Rui Rua, Jácome Cunha, João Paulo Fernandes, João Saraiva

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

This paper presents a study of the runtime, memory usage and energy consumption of twenty seven well-known software languages. We monitor the performance of such languages using ten different programming problems, expressed in each of the languages. Our results show interesting findings, such as, slower/faster languages consuming less/more energy, and how memory usage influences energy consumption. We show how to use our results to provide software engineers support to decide which language to use when energy efficiency is a concern.

Original languageEnglish (US)
Title of host publicationSLE 2017 - Proceedings of the 10th ACM SIGPLAN International Conference on Software Language Engineering, co-located with SPLASH 2017
EditorsBernhard Rumpe, Marjan Mernik, Benoit Combemale
PublisherAssociation for Computing Machinery, Inc
Pages256-267
Number of pages12
ISBN (Electronic)9781450355254
DOIs
StatePublished - Oct 23 2017
Event10th ACM SIGPLAN International Conference on Software Language Engineering, SLE 2017 - Vancouver, Canada
Duration: Oct 23 2017Oct 24 2017

Publication series

NameSLE 2017 - Proceedings of the 10th ACM SIGPLAN International Conference on Software Language Engineering, co-located with SPLASH 2017

Conference

Conference10th ACM SIGPLAN International Conference on Software Language Engineering, SLE 2017
Country/TerritoryCanada
CityVancouver
Period10/23/1710/24/17

Keywords

  • Energy Efficiency
  • Green Software
  • Language Benchmarking
  • Programming Languages

ASJC Scopus subject areas

  • Computer Science Applications
  • Software

Fingerprint

Dive into the research topics of 'Energy efficiency across programming languages: How do energy, time, and memory relate?'. Together they form a unique fingerprint.

Cite this