<node id="632980">
  <nid>632980</nid>
  <type>event</type>
  <uid>
    <user id="27707"><![CDATA[27707]]></user>
  </uid>
  <created>1582727996</created>
  <changed>1582727996</changed>
  <title><![CDATA[PhD Defense by Ashish Bijlani]]></title>
  <body><![CDATA[<p><strong>Title</strong>: Smart Storage for Smart Mobile Devices</p>

<p>&nbsp;</p>

<p><strong>Ashish Bijlani</strong></p>

<p>Ph.D. Student</p>

<p>School of Computer Science</p>

<p>Georgia Institute of Technology</p>

<p>&nbsp;</p>

<p><strong>Date</strong>: Tuesday, March 10th, 2020</p>

<p><strong>Time</strong>: 9:00 - 11:00am EDT</p>

<p><strong>Location</strong>: Klaus 1212</p>

<p>&nbsp;</p>

<p><strong>Committee</strong></p>

<p>Dr. Umakishore Ramachandran (Advisor,&nbsp;School of Computer Science, Georgia Institute of&nbsp;Technology)</p>

<p>Dr. Mostafa Ammar (School of Computer Science, Georgia Institute of&nbsp;Technology)</p>

<p>Dr. Ada Gavrilovska (School of Computer Science, Georgia Institute of&nbsp;Technology)</p>

<p>Dr. Vivek Sarkar (School of Computer Science, Georgia Institute of&nbsp;Technology)</p>

<p>Dr.&nbsp;Raghupathy Sivakumar&nbsp;(School of Electrical and Computer Engineering,&nbsp;Georgia Institute of&nbsp;Technology)</p>

<p>&nbsp;</p>

<p><strong>Abstract</strong></p>

<p>Smart mobile devices have largely evolved as primary tools for everyday personal computing needs. This has&nbsp;led to a surge of apps for communication, travel and planning, gaming, health tracking, social networking, home&nbsp;automation, media, and entertainment. Personal mobile devices are also increasingly being used for work. The&nbsp;versatility of these devices, however, poses high, and often conflicting, storage demands. As a result, devices&nbsp;quickly run out of space given their limited storage capacity.&nbsp;&nbsp;</p>

<p><br />
This work aims to address the storage management challenges on smart mobile devices. We begin by carrying&nbsp;out a large-scale longitudinal study of millions of mobile apps to report increase in their sizes over time.&nbsp;&nbsp;While&nbsp;historically small in size (25MB), our results show that modern mobile apps have evolved as feature-rich, large&nbsp;packages, each capable of consuming up to 4GB of storage space.&nbsp;&nbsp;Developers create &ldquo;build once, run&nbsp;everywhere&rdquo; apps to target multiple CPU architectures and demographics regions that consume redundant storage, despite Google&rsquo;s&nbsp;effort to create small apps. We further show that as apps become popular, developers pack more features to&nbsp;create to&nbsp;engage users, resulting in bigger apps. Yet, apps are not constrained by storage quota limits, and developers&nbsp;freely exploit persistent storage by hoarding data and frequently caching content as needed to offer high&nbsp;performance and rich user experience.&nbsp;<br />
<br />
This work further leverages results from a user study in the wild to show that users only use a small fraction of apps and features, and the usage is highly&nbsp;correlated to user context (e.g., location, day, time).&nbsp;Drawing&nbsp;upon our findings, we proposes a context-sensitive quota model for efficient and&nbsp;application-transparent storage management of smart devices. Storage space consumed by contextually&nbsp;unwanted apps/data is temporarily reclaimed by employing multiple techniques, such as&nbsp;selective&nbsp;compression, deletion, content adaptation, offline deduplication, and Cloud-backed hierarchical management.&nbsp;Reclaimed data is reconstructed proactively under predictive usage or served on-demand either by&nbsp;computation on the device or fetching it from the Cloud. To understand the design implications, we have&nbsp;implemented a platform storage service on Android that performs proactive management of local storage.&nbsp;Attributed to our highly optimized framework design, our prototype implementation imposes negligible runtime&nbsp;overhead and can free up significant storage space.</p>
]]></body>
  <field_summary_sentence>
    <item>
      <value><![CDATA[Smart Storage for Smart Mobile Devices]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_summary>
  <field_time>
    <item>
      <value><![CDATA[2020-03-10T10:00:00-04:00]]></value>
      <value2><![CDATA[2020-03-10T12:00:00-04:00]]></value2>
      <rrule><![CDATA[]]></rrule>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_time>
  <field_fee>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_fee>
  <field_extras>
      </field_extras>
  <field_audience>
          <item>
        <value><![CDATA[Faculty/Staff]]></value>
      </item>
          <item>
        <value><![CDATA[Public]]></value>
      </item>
          <item>
        <value><![CDATA[Graduate students]]></value>
      </item>
          <item>
        <value><![CDATA[Undergraduate students]]></value>
      </item>
      </field_audience>
  <field_media>
      </field_media>
  <field_contact>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_contact>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_phone>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_phone>
  <field_url>
    <item>
      <url><![CDATA[]]></url>
      <title><![CDATA[]]></title>
            <attributes><![CDATA[]]></attributes>
    </item>
  </field_url>
  <field_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_email>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>221981</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[Graduate Studies]]></item>
      </og_groups_both>
  <field_categories>
          <item>
        <tid>1788</tid>
        <value><![CDATA[Other/Miscellaneous]]></value>
      </item>
      </field_categories>
  <field_keywords>
          <item>
        <tid>100811</tid>
        <value><![CDATA[Phd Defense]]></value>
      </item>
      </field_keywords>
  <field_userdata><![CDATA[]]></field_userdata>
</node>
