Changeset 968 for docs


Ignore:
Timestamp:
Mar 22, 2011, 8:51:25 AM (8 years ago)
Author:
cameron
Message:

Some introductory remarks and notes

File:
1 edited

Legend:

Unmodified
Added
Removed
  • docs/PACT2011/01-intro.tex

    r949 r968  
    11\section{Introduction}
     2
     3Extensible Markup Language (XML) is a core technology standard
     4of the World-Wide Web Consortium (W3C) that provides a common
     5framework for encoding and communicating structured information
     6of all kinds.   In applications ranging from Office Open XML in
     7Microsoft Office to NDFD XML of the NOAA National Weather
     8Service, from KML in Google Earth to Castor XML in the Martian Rovers,
     9from ebXML for e-commerce data interchange to RSS for news feeds
     10from web sites everywhere, XML plays a ubiquitous role in providing
     11a common framework for data interoperability world-wide and beyond.
     12As XML 1.0 editor Tim Bray is quoted in the W3C celebration of XML at 10 years,
     13"there is essentially no computer in the world, desk-top, hand-held,
     14or back-room, that doesn't process XML sometimes."
     15
     16With all this XML processing, the performance of XML parsers
     17has attracted considerable attention.
     18Briefly discuss/cite XML chip, XML FPGA, multicore XML acceleration
     19Our own work ...
     20
     21But what about energy?  How many joules per hour are spent in
     22XML processing?  Do performance improvements necessarily translate
     23into energy savings?   Or does multicore parallelism actually
     24increase the energy cost with extra work required for interthread
     25synchronization?
     26
     27In this paper, we study the issues of energy and performance
     28of XML parsing.   [We would like to make the strong claim that
     29of all approaches to parallel XML parsing, ours has the
     30greatest potential for world-wide energy savings....]
    231
    332
     
    938%While the capabilities and users' expectations of mobile devices has rapidly increased, little imp%rovement to battery technology itself is foreseen in the near future \cite{silven2007, walker2007}.
    1039
    11 One area in which both servers and mobile devices devote considerable
    12 computational effort into is in the processing of Extensible Markup
    13 Language (XML) documents.  It was predicted that corporate servers
    14 would see a ``growth in XML traffic\ldots from 15\% [of overall
    15 network traffic] in 2004 to just under 48\% by 2008''
    16 \cite{coyle2005}.  Further, ``from the point of view of server
    17 efficiency[,] XML\ldots is the closest thing there is to a ubiquitous
    18 computing workload'' \cite{leventhal2009}.  In other words, XML is the
    19 quickly becoming the backbone of most server/server and client/server
    20 information exchanges.  Similarly, there is growing interest in the
    21 use of mobile web services for personalization, context-awareness, and
    22 content-adaptation of mobile web sites---most of which rely on XML
    23 \cite{canali2009}.  Whether the end user realizes it or not, XML is
    24 part of their daily life.
     40%One area in which both servers and mobile devices devote considerable
     41%computational effort into is in the processing of Extensible Markup
     42%Language (XML) documents.  It was predicted that corporate servers
     43%would see a ``growth in XML traffic\ldots from 15\% [of overall
     44%network traffic] in 2004 to just under 48\% by 2008''
     45%\cite{coyle2005}.  Further, ``from the point of view of server
     46%efficiency[,] XML\ldots is the closest thing there is to a ubiquitous
     47%computing workload'' \cite{leventhal2009}.  In other words, XML is the
     48%quickly becoming the backbone of most server/server and client/server
     49%%information exchanges.  Similarly, there is growing interest in the
     50%use of mobile web services for personalization, context-awareness, and
     51%content-adaptation of mobile web sites---most of which rely on XML
     52%\cite{canali2009}.  Whether the end user realizes it or not, XML is
     53%part of their daily life.
    2554
    26 Why are XML parsers important ?
    27 Talk about XML parsers and what they do in general.
    28 Brief few lines about byte-at-time ?
    29 What's new with Parabix style approach ?
    30 Introduce Parabix1 and Parabix2 ?
    31 Present overall quantiative improvements compared to other parsers.
     55%Why are XML parsers important ?
     56%Talk about XML parsers and what they do in general.
     57%Brief few lines about byte-at-time ?
     58%What's new with Parabix style approach ?
     59%Introduce Parabix1 and Parabix2 ?
     60%Present overall quantiative improvements compared to other parsers.
     61
     62
     63
     64
Note: See TracChangeset for help on using the changeset viewer.