Difference: WeeklySeminar (568 vs. 569)

Revision 5692019-06-17 - LeopoldoTeixeira

Line: 1 to 1
 
META TOPICPARENT name="SoftwareProductivityGroup"

GENTeS

Line: 21 to 21
 

Next Meeting

Changed:
<
<
Date and Time: May 15th, 15h
>
>
Date and Time: June 19th, 15h
  Location: CIn Amphitheatre
Changed:
<
<
Theme (presentation): Recommending Energy-Efficient Java Collections
>
>
Theme (presentation): Que fatores influenciam na ocorrência de conflitos de merge?
 
Changed:
<
<
Leader: Wellington Oliveira
>
>
Leader: Klissiomara Dias
 
Deleted:
<
<
Abstract: Over the last years, increasing attention has been given to creating energy-efficient software systems. However, developers still lack the knowledge and the tools to support them in that task. In this work, we explore our vision that energy consumption non-specialists can build software that consumes less energy by alternating, at development time, between thirdparty, readily available, diversely-designed pieces of software, without increasing the development complexity. To support our vision, we propose an approach for energy-aware development that combines the construction of application-independent energy profiles of Java collections and static analysis to produce an estimate of in which ways and how intensively a system employs these collections. By combining these two pieces of information, it is possible to produce energy-saving recommendations for alternative collection implementations to be used in different parts of the system. We implement this approach in a tool named CT+ that works with both desktop and mobile Java systems, and is capable of analyzing 40 different collection implementations of lists, maps, and sets. We applied CT+ to twelve software systems: two mobile-based, seven desktop-based, and three that can run in both environments. Our evaluation infrastructure involved a high-end server, a notebook, and three mobile devices. When applying the (mostly trivial) recommendations, we achieved up to 17.34% reduction in energy consumption just by replacing collection implementations. Even for a real world, mature, highlyoptimized system such as Xalan, CT+ could achieve a 5.81% reduction in energy consumption. Our results indicate that some widely used collections, e.g., ArrayList, HashMap, and HashTable, are not energy-efficient and sometimes should be avoided when energy consumption is a major concern.

Preprint: http://gustavopinto.org/lost+found/msr2019a.pdf

 

Planned Schedule for Next Meetings (subject to change)

Line: 40 to 37
 

2019 Meetings

Date Theme Leader
Added:
>
>
15/05 Recommending Energy-Efficient Java Collections Wellington Oliveira
 
24/04 Detecting Semantic Conflicts and Feature Interaction Paulo Borba
17/04 Replication studies considered harmful Leopoldo Teixeira
03/04 Advantages and disadvantages of a monolithic repository: a case study at google Paulo Borba
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback

mersin escort bayan adana escort bayan izmit escort ankara escort bursa escort