CHAPTER -1
INTRODUCTION
When data are available both on the local disk and on the server via
wireless network, an intuitive choice would be to access the data from the
local disk to save communication cost.
Idle,
Standby,
Sleep.
1.1.1.Active State:
1.1.2.Idle State:
In the idle state disk platters keep spinning with no data transfer.
1.1.3.Standby State:
In the standby state the disk is spun down, disk electronics are
partially Unpowered, and disk heads are unloaded or parked.
1.1.4.Sleep State:
In the sleep state all the remaining electronics are powered off, and a
hard reset is needed to reactivate the disk.
To save energy, disk is spun down to the standby state if it has been
idle for a threshold period of time, and to service a request it has to be spun
up to the active state.
1.1.5.Busy Period:
We call the time period between the disk spin-up and its adjacent
spin-down a busy period.
1.1.6.Quiet Period:
The time period between the disk spin-down and its adjacent spin-up a
quiet period. Because of substantial energy consumption with disk state
changes, the quiet period must be sufficiently long to justify the energy cost
for the disk spin-down/up.
1.1.7.Break-even time:
The minimum length of quiet period to pay off the cost is referred to
as the break-even time.
That is, if a disk stays in the standby state for a period of time that is
less than the break-even time, it consumes more energy, rather than saves
energy, by spinning down the disk.
If data requests are always first attempted at the hard disk, quiet
periods can be broken into pieces that are shorter than the break-even time
and render the spin-down energy saving efforts fruitless, or even harmful.
In the CAM mode, the wireless card keeps active with high power
consumption.
In the PSM mode, the wireless card turns radio off and periodically
wakes up to check with access point.
Data transmission can be carried out in both CAM and PSM, but with
different latencies and bandwidths. While there is also time and energy cost
for the mode changes, the cost is smaller than that for the hard disk.
CHAPTER -2
LITERATURE SURVEY:
Figure 2.2 The Energy Consumption Parameters for the Cisco Aironet
350 wireless card.
Compared with accessing local hard disk, the performance and energy
cost of accessing a remote storage via wireless card are sensitive to the
networking environment. For example, the bandwidth of WNIC highly relies
on the radio quality, which could be affected by many factors, such as
distance and physical geometry.
2.3.TRACES COLLECTION:
The blocks of the traced files are sequentially mapped to the local hard
disk with a small random distance between files to simulate a real layout of
files on the disk. We collected traces of six representative applications in a
mobile computing environment, as listed in Table2.3.
2.4.EXAMPLE SCENARIO’S:
In this work load, make requests a large number of small files, where
each request can incur a substantial latency and energy cost on the disk. So
WNIC with a low latency is more cost effective than the hard disk. BlueFS
consumes 2179J energy. In contrast FlexFetch consumes only 1522J, which
is even less than that for WNIC-only.
The data set of make is then mainly serviced by the WNIC, which is
energy efficient for non-bursty workloads. BlueFS, however, has no
knowledge of future accesses and solely relies on the recent history of data
accesses and current storage device status to make a choice, which makes it
lack a long-term view of energy consumption caused by different workload
access patterns.
As a result, it keeps switching between the hard disk and the remote
storage, which incurs significant energy consumption for both devices. With
the increase of WNIC latency, the energy consumption of WNIC-only
quickly increases and exceeds that of Disk-only.
11 Department Of Information Technology
Prevention Of Energy Loss in Mobile Computing Using FLEXFETCH Scheme
CHAPTER -3
SYSTEM ANALYSIS
3.1.EXISTING SYSTEM:
BlueFS uses a read from any, write to many strategy. A kernel module
redirects file system calls to a user-level daemon, called Wolverine, that
decides when and where to access data. For calls that read data, Wolverine
orders attached devices by the anticipated performance and energy cost of
fetching data, then attempts to read information from the least costly device.
This lets BlueFS adapt when portable storage devices are inserted or
removed,when the dynamic power management status of a device changes,
or when wireless network conditions fluctuate. For calls that write data,
Wolverine asynchronously replicates modifications to all devices attached to
a mobile computer. Wolverine aggregates modifications in per-device write
queues that are periodically flushed to storage devices.
3.1.1.Architecture of BlueFS:
BlueFS associates a 96-bit identifier with each object: the first 32 bits
specify an administrative volume , and the remaining 64 bits uniquely
identify the object within that volume. Caching in BlueFS is performed at
the block-level. Operations that read or modify data operate on whole 4KB
blocks this size was chosen to match the Linux page cache block size.
In the above Figure , BlueFS is fetching a large file with the disk
initially in standby mode to conserve power.
Using other file systems, fetching the first block incurs a large delay
as the disk spins up (800ms for the Hitachi microdrive and one second for
the IBM T20 laptop drive). In contrast, BlueFS hides this delay by fetching
blocks over the network.
For each block that it fetches from the network, BlueFS issues a ghost
hint that discloses the opportunity cost of the disk being in standby. While
the disk spins up in response to the ghost hints, BlueFS continues to fetch
blocks from the server. After the transition completes, BlueFS fetches
remaining blocks from disk. Eventually, the network device enters a power-
saving mode since it is now idle. No ghost hints are issued to the network
device because the disk offers both the lowest current and ideal cost.
3.1.3.Energy Efficiency:
In the below Figure, all files accessed by the trace are initially cached
on the microdrive. The left graph compares the interactive delay added to
trace replay by BlueFS and Coda this shows the time that the user waits for
19 Department Of Information Technology
Prevention Of Energy Loss in Mobile Computing Using FLEXFETCH Scheme
file operations to complete. The right graph shows the amount of additional
energy used by the iPAQ to execute file system operations (i.e. it excludes
energy expended during think time). Coda uses default powermanagement
(PSM for the network and the microdrive's ABLE power manager).
With 0ms latency, BlueFS reduces interactive delay by 35% and file
system energy usage by 31%. Since all files are on disk, Coda only uses the
network to asynchronously reintegrate modifications to the server. BlueFS,
however, achieves substantial performance and energy benet by fetching
small objects from the server and by using the network when the disk is in
standby. With 30ms network latency, the microdrive always offers better
performance than the server when it is active. In the absence of power
management, Coda's static hierarchy would always be correct.
3.1.4.Limitations of BlueFS:
There are several limitations in the BLUE FILE SYSTEM which are listed
as below:
Tracking recently received requests can only tell which device should
have been used for the optimal energy consumption, but cannot
confidently predict how much data will be accessed in the future.
3.2.PROPOSED SYSTEM:
The scheme tracks and records a program’s file access history, which
is independent of the I/O devices used or other environment settings such as
current wireless bandwidth. The recorded file access profile is then used to
adaptively determine the I/O source to service the requests in the next run of
the program.
CHAPTER -4
SYSTEM DESIGN:
4.1.BLOCK DIAGRAM:
4.2.DESCRIPTION:
INPUT UNIT:
It fetches the input from the user. It may be either be an write (WR)
instruction or read (RD) instruction.
PROCESSING UNIT:
OUTPUT UNIT:
4.3.2.Class Diagram:
Class diagrams are some of the most difficult UML diagrams to draw.
This will give a very high level overview of the process. They are composed
of three things: a name, attributes, and operations.
4.3.3.Activity Diagram:
4.3.3. a) Profiling:
4.3.3.b) Adaptation:
4.3.3.c)Re-evaluation:
4.3.4.Sequence Diagram:
These diagram shows the relationship between objects and the order
of messages passed by them. The objects are listed as icons and arrows
indicate the messages being passed between them. The numbers next to the
messages are called the sequence numbers.
5.SYSTEM IMPLEMENTATION:
5.2. DESCRIPTION:
The first step is to get the input from the user. Then we have to track
the RD/WR system calls and monitor the system modes. There are two types
of system modes.
The necessary operations are performed and the data’s are stored in
the respective storage devices. The final step is to Re-evaluate the existing
profile with the incoming new program. The necessary modifications are
done in the Re-evaluating stage.
The output the process is either we have the local disk or the wireless
network.
5.3.MODULES USED:
5.4.MODULES EXPLANATION:
leverage process group structure in Linux to associate all the file accesses
requested by processes belonging to the same group with the program.
The home form shows all the forms which we are using the project.
The Input read form is used to get the user Input’s. The user has to
give the input for the Request, Response, Request Time, Response Time.
Then it automatically calculates the Think time. If the Think Time is less
than 100, then we can go for profiling.
The user has to give the input for the Request, Response, Request
Time, Response Time. Then it automatically calculates the Think time. If the
Think Time is less than 50, then we can go for sequencing.
The user has to give the input for the Request, Response, Request
Time, Response Time. Then it automatically calculates the Think time. If the
Think Time is less than 30, then the Input read becomes disable.
evaluation stage. Profile-based decision about data source can be made for
each stage, which allows the profile accuracy and decision correctness to be
evaluated in a timely manner and necessary adjustments can be made
accordingly. When we have the profile and the program is to enter its first
evaluation stage, we estimate the execution times and energy costs for the
stage assuming disk or network is used, respectively, to determine I/O data
source, using the profile that has been recorded for the program.
In order to estimate execution times and energy costs for servicing I/O
requests on various data sources, we need to calculate the length of period of
time when a device stays at each power mode. To this end, we maintain an
on-line simulator for each device to emulate their power saving policies.
Such simulation causes minimal overhead, since only a small amount of
computation is needed.
According to the power saving models if the idle period between two
consecutive I/O requests is larger than a time-out threshold, the device
switches from a high-power mode (the active/idle mode for the disk and the
CAM mode for the wireless network card) to a low-power mode (the
standby mode for the disk and the PSM mode for the wireless network card).
For each request, its service time includes a latency and a transfer time.
The disk latency is calculated using the average seek and rotation
time, and an average network latency is used for the network card. The
transfer time can be derived from the request size and device bandwidth. If a
power mode transition is involved in servicing a request, the associated
energy and time overhead is counted in the estimation. Notice that the mode-
40 Department Of Information Technology
Prevention Of Energy Loss in Mobile Computing Using FLEXFETCH Scheme
switch threshold as well as its time and energy cost for the network card are
smaller than those for the disk, which makes wireless network a desired
alternative data source in some I/O access patterns.
In this way, we can estimate the execution time Tdisk and the energy
consumption Edisk for accessing data on the disk, and the execution time
Tnetwork and energy consumption Enetwork for servicing requests from a
remote storage server via network. FlexFetch optimizes energy usage for I/O
operations by treating equally the I/O energy cost and performance and
obeying a user-specified maximum tolerable I/O performance loss rate. A
threshold loss rate of m% means that FlexFetch will not switch to the other
I/O data source by saving x% energy consumption but extending I/O
execution time by n% if x<n or n>m. Asking for user to provide this kind of
preference, such as loss rate, is common in today’s battery-powered system,
such as the “Power manager” in the IBM ThinkPad laptop. Using the
estimated energy cost, execution time, and the user-specified performance
loss rate, we summarize the rules determining I/O data source for an
evaluation stage as follows:
In this way, in the current run of a program, its initial behaviors are
examined in a bigger history picture, and as time goes on, the current
behaviors will have more weight in the re-evaluation. Finally, the new
profile will be recorded to replace the old profile for future use at the end of
this run.
CHAPTER -6
6.1.3.System Testing:
6.1.4.Unit Testing:
6.1.5.Functional Tests:
Functional test cases involved exercising the code with nominal input
values for which the expected results are known, as well as boundary values
and special values, such as logically related inputs, files of identical
elements, and empty files.
6.1.6.Structured Test:
Testing begins at the module level and works “outward” toward the
integration of the entire computer based system.
Different testing techniques are appropriate at different points in time.
The developer of the software and an independent test group conducts
testing.
Testing and Debugging are different activities but debugging must be
accommodated in any testing strategy.
6.2.1.Program Testing:
The logical and syntax errors have been pointed out by program
testing. A syntax error is an error in a program statement that in violates one
or more rules of the language in which it is written. An improperly defined
field dimension or omitted keywords are common syntax error.
These errors are shown through error messages generated by the
computer. A logic error on the other hand deals with the incorrect data
fields, out-off-range items and invalid combinations. Since the compliers
will not deduct logical error, the programmer must examine the output.
Condition testing exercises the logical conditions contained in the module.
The possible types of elements in a condition include a Boolean operator,
Boolean variable, a pair of Boolean parentheses. A relational operator or on
arithmetic expression. Condition testing method focuses on testing each
condition in the program the purpose of condition test is to deduct not only
the errors in the condition of a program but also other a errors in the
program.
6.2.2.Validation Testing:
requirement. After validation test has been conducted, one of two conditions
exists.
The function or performance characteristics confirm to specifications
and are accepted.
A validation from specification is uncovered and a deficiency created.
CHAPTER -7
CONCLUSION:
CHAPTER - 8
FUTURE WORK:
CHAPTER 9
APPENDICES
/// <summary>
/// Clean up any resources being used.
/// </summary>
/// <param name="disposing">true if managed resources should be
disposed; otherwise, false.</param>
protected override void Dispose(bool disposing)
{
if (disposing && (components != null))
{
components.Dispose();
}
base.Dispose(disposing);
}
/// <summary>
/// Required method for Designer support - do not modify
/// the contents of this method with the code editor.
/// </summary>
private void InitializeComponent()
{
this.label1 = new System.Windows.Forms.Label();
this.panel1 = new System.Windows.Forms.Panel();
this.BtnEnd = new System.Windows.Forms.Button();
this.BtnFileHistory = new System.Windows.Forms.Button();
this.BtnProfileUpdation = new System.Windows.Forms.Button();
this.BtnAdaptiveSel = new System.Windows.Forms.Button();
this.BtnProfile = new System.Windows.Forms.Button();
this.Btnread = new System.Windows.Forms.Button();
this.panel1.SuspendLayout();
this.SuspendLayout();
//
// label1
//
this.label1.AutoSize = true;
this.BtnProfileUpdation.Click += new
System.EventHandler(this.BtnProfileUpdation_Click);
//
// BtnAdaptiveSel
//
this.BtnAdaptiveSel.Location = new System.Drawing.Point(108,
108);
this.BtnAdaptiveSel.Name = "BtnAdaptiveSel";
this.BtnAdaptiveSel.Size = new System.Drawing.Size(177, 23);
this.BtnAdaptiveSel.TabIndex = 9;
this.BtnAdaptiveSel.Text = "DataSource AdaptiveSelection";
this.BtnAdaptiveSel.UseVisualStyleBackColor = true;
this.BtnAdaptiveSel.Click += new
System.EventHandler(this.BtnAdaptiveSel_Click);
//
// BtnProfile
//
this.BtnProfile.Location = new System.Drawing.Point(108, 79);
this.BtnProfile.Name = "BtnProfile";
this.BtnProfile.Size = new System.Drawing.Size(177, 23);
this.BtnProfile.TabIndex = 8;
this.BtnProfile.Text = "Profiling Program Execution";
this.BtnProfile.UseVisualStyleBackColor = true;
this.BtnProfile.Click += new
System.EventHandler(this.BtnProfile_Click);
//
// Btnread
57 Department Of Information Technology
Prevention Of Energy Loss in Mobile Computing Using FLEXFETCH Scheme
//
this.Btnread.Location = new System.Drawing.Point(108, 50);
this.Btnread.Name = "Btnread";
this.Btnread.Size = new System.Drawing.Size(177, 23);
this.Btnread.TabIndex = 7;
this.Btnread.Text = "Input Read";
this.Btnread.UseVisualStyleBackColor = true;
this.Btnread.Click += new
System.EventHandler(this.Btnread_Click);
//
// Home
//
this.AutoScaleDimensions = new System.Drawing.SizeF(6F, 13F);
this.AutoScaleMode =
System.Windows.Forms.AutoScaleMode.Font;
this.ClientSize = new System.Drawing.Size(695, 419);
this.Controls.Add(this.panel1);
this.Controls.Add(this.label1);
this.Name = "Home";
this.Text = "Home";
this.panel1.ResumeLayout(false);
this.ResumeLayout(false);
this.PerformLayout();
#endregion
58 Department Of Information Technology
Prevention Of Energy Loss in Mobile Computing Using FLEXFETCH Scheme
The .NET framework was designed with three goals in mind. First it
was intended to make windows applications much more reliable, while also
providing an application with a greater degree of security. Second, it was
intended to simplify the development of the web applications and services
that not only work in the traditional sense, but no mobile devices as well.
Lastly the framework was to design to provide a single set of libraries that
will work with multiple languages.
Objects
classes.
Encapsulation.
Abstraction.
Inheritance.
Polymorphism.
CHAPTER 10
REFERENCES:
[2] F. Chen, S. Jiang, and X. Zhang. SmartSaver: Turning flash memory into
a disk energy saver for mobile computers. In Proc. of 2006 International
Symposium on Low Power Electronics and Design (ISLPED’06), 2006.
[10] E. Jung and N. Vaidya. A power control MAC protocol for Ad Hoc
networks. In Wireless Networks (ACM WINET), 2005.
ABSTRACT
TABLE OF CONTENT
CHAPTER TITLE
PAGE NO.
LIST OF FIGURES
vii
LIST OF TABLES
viii
LIST OF ABBREVATIONS
ix
1 INTRODUCTION
1
Wireless Network.
2 LITERATURE SURVEY
6
3 SYSTEM ANALYSIS
15
CHAPTER TITLE
PAGE NO.
4 SYSTEM DESIGN.
23
4.1 Block Diagram.
23
4.2 Description.
24
CHAPTER TITLE
PAGE NO.
LIST OF FIGURES
LIST OF TABLES
S.NO TITLE
PAGE NO
LIST OF ABBREVATIONS
CAM - Continuous Aware Mode.
PSM - Power Saving Mode.
WNIC - Wireless Network Interface Card.