1 / 13

Outline

This study explores the issue of file hoarding for mobile computers in the context of ubiquitous computing. It examines various approaches, including user input, snap-shot spying, and transparent analytical spying, to create efficient hoarding profiles. The implementation issues and the need for hoarding in the era of cheaper and larger storage options are also discussed.

danal
Download Presentation

Outline

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Outline • Intelligent file hoarding for mobile computers Carl Tait, Hui Lei, Swarup Acharya and Henry Chang Mobicom ‘95 Ubiquitous Computing

  2. Hoarding • Prefetching and storing objects for access when the network is disconnected or weakly-connected • E.g. Internet Explorer lets you browse web pages Offline. Avantgo lets you access web pages offline in PDAs. I download power point slides for this presentation into the laptop Ubiquitous Computing

  3. Problem • Local storage space is limited. How do I hoard all the data that I need so that I can continue to work, while I’m offline? • Suppose I have 80 GB worth of files in the connected machine. I have a 20 GB hard drive in the mobile computer, how can I copy files such that I can continue to work without disruption? • Suppose I have 80 GB hard drive in the mobile device, hoarding profile is not necessary. Ubiquitous Computing

  4. Problem • User input is necessary. • Users should say what they want to be hoarded for disconnected access. But, users do not know what files they really need. They can tell that they need Powerpoint. But they can’t say that they also need some .dll file that is needed to print the presentation onto a laser printer (say) Ubiquitous Computing

  5. Approaches to create hoard profiles • Do Nothing: • Run the application that you intend to use on the road. Normal caching mechanism would’ve stored the documents for later access • Problem is that, there are no “typical” runs. Every program run is different, just because it worked while connected does not mean that it will work while disconnected Ubiquitous Computing

  6. User Provided Information • Coda uses this approach. The users specify the files that they want to be hoarded. • Most of the time, users do not even know what files they need. Problem of hidden files and critical files that are rarely used Ubiquitous Computing

  7. Snap-shot spying: • System keeps track of all files access between some markers. You specify <START SPYING> and <END SPYING> messages to refine files. • Semantic Distance: • Seer system looked at the semantic distance between files to predict related files Ubiquitous Computing

  8. Transparent, analytical spying • Automatically detect working sets for applications and data • Provide generalized bookends to delimit periods of activity • Present convenient bundles to the user using a GUI • Let the users “load the briefcase” Ubiquitous Computing

  9. Detection of working set • Working set defines that set of files that are part of a program execution. This may include data files, shared libraries (DLLs), related applications • Log file accesses to create program execution tree. Subsequent executions of program help refine this tree • Problem is differentiating application vs user data, you want to learn the “application” from my executions of the application, not the files that I operated on Ubiquitous Computing

  10. Differentiate application and data • File name extensions (.exe, .bat, .ini etc) • Directory inferencing (/usr/include/file.h is related to application, /home/surendar/data/foo.dat is related to data) • Timestamps – Files modified at the same time as application probably belong with application Ubiquitous Computing

  11. Generalized bookends • Measure all files and applications accessed during the time intervals • Generalize data over multiple executions • Presentation and Selection – GUI tools Ubiquitous Computing

  12. Implementation issues • Data orphan problem • Local program accesses remote data • Program orphan problem • Remote program accessing only local data • GUI tools to select files for hoarding Ubiquitous Computing

  13. Discussion • As disks become cheaper, smaller and larger, is hoarding needed? 1 GB IBM Microdrive Ubiquitous Computing

More Related