Thinking Clearly About Performance, Part 1.

The article presents information on axiomatic methods for optimizing computer software performance. The usefulness of axiomatic reasoning for ensuring clear and testable improvements is discussed. It is noted that the majority of software performance improvements involve speed of response. Various e...

Descripción completa

Detalles Bibliográficos
Publicado en:Communications of the ACM Vol. 53; no. 9; pp. 55 - 61
Autor principal: MILLSAP, CARY
Formato: Artículo
Publicado: Association for Computing Machinery Sep2010
Materias:
Acceso en línea:Ver este registro en EBSCOhost
fields @attributes:
  recordID: 1
pdfLink:
plink: https://search.ebscohost.com/login.aspx?direct=true&db=hlh&AN=53529231&site=ehost-live
header:
  @attributes:
    shortDbName: hlh
    uiTerm: 53529231
    longDbName: Humanities International Complete
    uiTag: AN
  controlInfo:
    bkinfo:
    jinfo:
      jid:
        00010782
        ACM
      jtl: Communications of the ACM
      issn: 00010782
      maglogo: N
    pubinfo:
      dt: Sep2010
      vid: 53
      iid: 9
      pid: 68
      pub: Association for Computing Machinery
    artinfo:
      ui:
        53529231
        10.1145/1810891.1810909
      ppf: 55
      ppct: 6
      formats:
      tig:
        atl: Thinking Clearly About Performance, Part 1.
      aug:
        au: MILLSAP, CARY
        affil: President of Method R Corporation.
      su:
        Information services management
        Application software
        Mathematical optimization
        Computer programming
        Computer software
        Axioms
      sug:
        subj:
          Information services management
          Application software
          Mathematical optimization
          Computer programming
          Computer software
          Axioms
      ab: The article presents information on axiomatic methods for optimizing computer software performance. The usefulness of axiomatic reasoning for ensuring clear and testable improvements is discussed. It is noted that the majority of software performance improvements involve speed of response. Various examples of how a solution which seems to work well in theory can actually fail in practice are provided. Replacing simple averages with distribution percentages is recommended as a means of identifying problems more accurately.
      pubtype: Periodical
      doctype: Article
      src: R
    language: English
    refInfo:
    copyright:
      @attributes:
        flag: Y
      dt:
        @attributes:
          year: 2010
    holdings:
      @attributes:
        islocal: N