January 5, 2020 Conference paper Closed Access

Yiqun Chen; Stefan Winter; Neeraj Suri

MARC21 XML Export

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2020-01-05</subfield>
  </datafield>
  <controlfield tag="005">20210219002704.0</controlfield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">doi</subfield>
    <subfield code="i">isVersionOf</subfield>
    <subfield code="a">10.5281/zenodo.3598077</subfield>
  </datafield>
  <controlfield tag="001">3598078</controlfield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="o">oai:zenodo.org:3598078</subfield>
  </datafield>
  <datafield tag="711" ind1=" " ind2=" ">
    <subfield code="d">Oct 28 - 31, 2019</subfield>
    <subfield code="g">ISSRE</subfield>
    <subfield code="a">International Symposium on Software Reliability Engineering</subfield>
    <subfield code="c">Berlin, Germany</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">&lt;p&gt;Performance bugs, i.e., program source code that&amp;nbsp;is unnecessarily inefficient, have received significant attention&amp;nbsp;by the research community in recent years. A number of&amp;nbsp;empirical studies have investigated how these bugs differ from&amp;nbsp;&amp;ldquo;ordinary&amp;rdquo; bugs that cause functional deviations and several&amp;nbsp;approaches to aid their detection, localization, and removal have&amp;nbsp;been proposed. Many of these approaches focus on certain subclasses&amp;nbsp;of performance bugs, e.g., those resulting from redundant&amp;nbsp;computations or unnecessary synchronization, and the evaluation&amp;nbsp;of their effectiveness is usually limited to a small number of&amp;nbsp;known instances of these bugs. To provide researchers working&amp;nbsp;on performance bug detection and localization techniques with&amp;nbsp;a larger corpus of performance bugs to evaluate against, we&amp;nbsp;conduct a study of more than 700 performance bug fixing&amp;nbsp;commits across 13 popular open source projects written in C&amp;nbsp;and C++ and investigate the relative frequency of bug types as&amp;nbsp;well as their complexity. Our results show that many of these&amp;nbsp;fixes follow a small set of bug patterns, that they are contributed&amp;nbsp;by experienced developers, and that the number of lines needed&amp;nbsp;to fix performance bugs is highly project dependent.&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">DEEDS Group, Dept. of Computer Science Technische Universit¨at Darmstadt</subfield>
    <subfield code="a">Stefan Winter</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">DEEDS Group, Dept. of Computer Science Technische Universit¨at Darmstadt</subfield>
    <subfield code="a">Neeraj Suri</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">closed</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="y">Conference website</subfield>
    <subfield code="u">http://2019.issre.net/node/79</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">conferencepaper</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">DEEDS Group, Dept. of Computer Science Technische Universit¨at Darmstadt</subfield>
    <subfield code="a">Yiqun Chen</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.3598078</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Inferring Performance Bug Patterns from Developer Commits</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="c">830927</subfield>
    <subfield code="a">Cyber security cOmpeteNCe fOr Research anD InnovAtion</subfield>
  </datafield>
</record>