\documentclass[11pt,twoside]{article}\makeatletter

\IfFileExists{xcolor.sty}%
  {\RequirePackage{xcolor}}%
  {\RequirePackage{color}}
\usepackage{colortbl}
\usepackage{wrapfig}
\usepackage{ifxetex}
\ifxetex
  \usepackage{fontspec}
  \usepackage{xunicode}
  \catcode`⃥=\active \def⃥{\textbackslash}
  \catcode`❴=\active \def❴{\{}
  \catcode`❵=\active \def❵{\}}
  \def\textJapanese{\fontspec{Noto Sans CJK JP}}
  \def\textChinese{\fontspec{Noto Sans CJK SC}}
  \def\textKorean{\fontspec{Noto Sans CJK KR}}
  \setmonofont{DejaVu Sans Mono}
  
\else
  \IfFileExists{utf8x.def}%
   {\usepackage[utf8x]{inputenc}
      \PrerenderUnicode{–}
    }%
   {\usepackage[utf8]{inputenc}}
  \usepackage[english]{babel}
  \usepackage[T1]{fontenc}
  \usepackage{float}
  \usepackage[]{ucs}
  \uc@dclc{8421}{default}{\textbackslash }
  \uc@dclc{10100}{default}{\{}
  \uc@dclc{10101}{default}{\}}
  \uc@dclc{8491}{default}{\AA{}}
  \uc@dclc{8239}{default}{\,}
  \uc@dclc{20154}{default}{ }
  \uc@dclc{10148}{default}{>}
  \def\textschwa{\rotatebox{-90}{e}}
  \def\textJapanese{}
  \def\textChinese{}
  \IfFileExists{tipa.sty}{\usepackage{tipa}}{}
\fi
\def\exampleFont{\ttfamily\small}
\DeclareTextSymbol{\textpi}{OML}{25}
\usepackage{relsize}
\RequirePackage{array}
\def\@testpach{\@chclass
 \ifnum \@lastchclass=6 \@ne \@chnum \@ne \else
  \ifnum \@lastchclass=7 5 \else
   \ifnum \@lastchclass=8 \tw@ \else
    \ifnum \@lastchclass=9 \thr@@
   \else \z@
   \ifnum \@lastchclass = 10 \else
   \edef\@nextchar{\expandafter\string\@nextchar}%
   \@chnum
   \if \@nextchar c\z@ \else
    \if \@nextchar l\@ne \else
     \if \@nextchar r\tw@ \else
   \z@ \@chclass
   \if\@nextchar |\@ne \else
    \if \@nextchar !6 \else
     \if \@nextchar @7 \else
      \if \@nextchar (8 \else
       \if \@nextchar )9 \else
  10
  \@chnum
  \if \@nextchar m\thr@@\else
   \if \@nextchar p4 \else
    \if \@nextchar b5 \else
   \z@ \@chclass \z@ \@preamerr \z@ \fi \fi \fi \fi
   \fi \fi  \fi  \fi  \fi  \fi  \fi \fi \fi \fi \fi \fi}
\gdef\arraybackslash{\let\\=\@arraycr}
\def\@textsubscript#1{{\m@th\ensuremath{_{\mbox{\fontsize\sf@size\z@#1}}}}}
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\def\abbr{}
\def\corr{}
\def\expan{}
\def\gap{}
\def\orig{}
\def\reg{}
\def\ref{}
\def\sic{}
\def\persName{}\def\name{}
\def\placeName{}
\def\orgName{}
\def\textcal#1{{\fontspec{Lucida Calligraphy}#1}}
\def\textgothic#1{{\fontspec{Lucida Blackletter}#1}}
\def\textlarge#1{{\large #1}}
\def\textoverbar#1{\ensuremath{\overline{#1}}}
\def\textquoted#1{‘#1’}
\def\textsmall#1{{\small #1}}
\def\textsubscript#1{\@textsubscript{\selectfont#1}}
\def\textxi{\ensuremath{\xi}}
\def\titlem{\itshape}
\newenvironment{biblfree}{}{\ifvmode\par\fi }
\newenvironment{bibl}{}{}
\newenvironment{byline}{\vskip6pt\itshape\fontsize{16pt}{18pt}\selectfont}{\par }
\newenvironment{citbibl}{}{\ifvmode\par\fi }
\newenvironment{docAuthor}{\ifvmode\vskip4pt\fontsize{16pt}{18pt}\selectfont\fi\itshape}{\ifvmode\par\fi }
\newenvironment{docDate}{}{\ifvmode\par\fi }
\newenvironment{docImprint}{\vskip 6pt}{\ifvmode\par\fi }
\newenvironment{docTitle}{\vskip6pt\bfseries\fontsize{22pt}{25pt}\selectfont}{\par }
\newenvironment{msHead}{\vskip 6pt}{\par}
\newenvironment{msItem}{\vskip 6pt}{\par}
\newenvironment{rubric}{}{}
\newenvironment{titlePart}{}{\par }

\newcolumntype{L}[1]{){\raggedright\arraybackslash}p{#1}}
\newcolumntype{C}[1]{){\centering\arraybackslash}p{#1}}
\newcolumntype{R}[1]{){\raggedleft\arraybackslash}p{#1}}
\newcolumntype{P}[1]{){\arraybackslash}p{#1}}
\newcolumntype{B}[1]{){\arraybackslash}b{#1}}
\newcolumntype{M}[1]{){\arraybackslash}m{#1}}
\definecolor{label}{gray}{0.75}
\def\unusedattribute#1{\sout{\textcolor{label}{#1}}}
\DeclareRobustCommand*{\xref}{\hyper@normalise\xref@}
\def\xref@#1#2{\hyper@linkurl{#2}{#1}}
\begingroup
\catcode`\_=\active
\gdef_#1{\ensuremath{\sb{\mathrm{#1}}}}
\endgroup
\mathcode`\_=\string"8000
\catcode`\_=12\relax

\usepackage[a4paper,twoside,lmargin=1in,rmargin=1in,tmargin=1in,bmargin=1in,marginparwidth=0.75in]{geometry}
\usepackage{framed}

\definecolor{shadecolor}{gray}{0.95}
\usepackage{longtable}
\usepackage[normalem]{ulem}
\usepackage{fancyvrb}
\usepackage{fancyhdr}
\usepackage{graphicx}
\usepackage{marginnote}

\renewcommand{\@cite}[1]{#1}


\renewcommand*{\marginfont}{\itshape\footnotesize}

\def\Gin@extensions{.pdf,.png,.jpg,.mps,.tif}

  \pagestyle{fancy}

\usepackage[pdftitle={Fault Tolerant Scheduling of Partitioned and Grouped Jobs in Grid Computing (FTPG)},
 pdfauthor={}]{hyperref}
\hyperbaseurl{}

	 \paperwidth210mm
	 \paperheight297mm
              
\def\@pnumwidth{1.55em}
\def\@tocrmarg {2.55em}
\def\@dotsep{4.5}
\setcounter{tocdepth}{3}
\clubpenalty=8000
\emergencystretch 3em
\hbadness=4000
\hyphenpenalty=400
\pretolerance=750
\tolerance=2000
\vbadness=4000
\widowpenalty=10000

\renewcommand\section{\@startsection {section}{1}{\z@}%
     {-1.75ex \@plus -0.5ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large\bfseries}}
\renewcommand\subsection{\@startsection{subsection}{2}{\z@}%
     {-1.75ex\@plus -0.5ex \@minus- .2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\Large}}
\renewcommand\subsubsection{\@startsection{subsubsection}{3}{\z@}%
     {-1.5ex\@plus -0.35ex \@minus -.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\large}}
\renewcommand\paragraph{\@startsection{paragraph}{4}{\z@}%
     {-1ex \@plus-0.35ex \@minus -0.2ex}%
     {0.5ex \@plus .2ex}%
     {\reset@font\normalsize}}
\renewcommand\subparagraph{\@startsection{subparagraph}{5}{\parindent}%
     {1.5ex \@plus1ex \@minus .2ex}%
     {-1em}%
     {\reset@font\normalsize\bfseries}}


\def\l@section#1#2{\addpenalty{\@secpenalty} \addvspace{1.0em plus 1pt}
 \@tempdima 1.5em \begingroup
 \parindent \z@ \rightskip \@pnumwidth 
 \parfillskip -\@pnumwidth 
 \bfseries \leavevmode #1\hfil \hbox to\@pnumwidth{\hss #2}\par
 \endgroup}
\def\l@subsection{\@dottedtocline{2}{1.5em}{2.3em}}
\def\l@subsubsection{\@dottedtocline{3}{3.8em}{3.2em}}
\def\l@paragraph{\@dottedtocline{4}{7.0em}{4.1em}}
\def\l@subparagraph{\@dottedtocline{5}{10em}{5em}}
\@ifundefined{c@section}{\newcounter{section}}{}
\@ifundefined{c@chapter}{\newcounter{chapter}}{}
\newif\if@mainmatter 
\@mainmattertrue
\def\chaptername{Chapter}
\def\frontmatter{%
  \pagenumbering{roman}
  \def\thechapter{\@roman\c@chapter}
  \def\theHchapter{\roman{chapter}}
  \def\thesection{\@roman\c@section}
  \def\theHsection{\roman{section}}
  \def\@chapapp{}%
}
\def\mainmatter{%
  \cleardoublepage
  \def\thechapter{\@arabic\c@chapter}
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \pagenumbering{arabic}
  \setcounter{secnumdepth}{6}
  \def\@chapapp{\chaptername}%
  \def\theHchapter{\arabic{chapter}}
  \def\thesection{\@arabic\c@section}
  \def\theHsection{\arabic{section}}
}
\def\backmatter{%
  \cleardoublepage
  \setcounter{chapter}{0}
  \setcounter{section}{0}
  \setcounter{secnumdepth}{2}
  \def\@chapapp{\appendixname}%
  \def\thechapter{\@Alph\c@chapter}
  \def\theHchapter{\Alph{chapter}}
  \appendix
}
\newenvironment{bibitemlist}[1]{%
   \list{\@biblabel{\@arabic\c@enumiv}}%
       {\settowidth\labelwidth{\@biblabel{#1}}%
        \leftmargin\labelwidth
        \advance\leftmargin\labelsep
        \@openbib@code
        \usecounter{enumiv}%
        \let\p@enumiv\@empty
        \renewcommand\theenumiv{\@arabic\c@enumiv}%
	}%
  \sloppy
  \clubpenalty4000
  \@clubpenalty \clubpenalty
  \widowpenalty4000%
  \sfcode`\.\@m}%
  {\def\@noitemerr
    {\@latex@warning{Empty `bibitemlist' environment}}%
    \endlist}

\def\tableofcontents{\section*{\contentsname}\@starttoc{toc}}
\parskip0pt
\parindent1em
\def\Panel#1#2#3#4{\multicolumn{#3}{){\columncolor{#2}}#4}{#1}}
\newenvironment{reflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemsep}{0pt}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\itshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{sansreflist}{%
  \begin{raggedright}\begin{list}{}
  {%
   \setlength{\topsep}{0pt}%
   \setlength{\rightmargin}{0.25in}%
   \setlength{\itemindent}{0pt}%
   \setlength{\parskip}{0pt}%
   \setlength{\itemsep}{0pt}%
   \setlength{\parsep}{2pt}%
   \def\makelabel##1{\upshape ##1}}%
  }
  {\end{list}\end{raggedright}}
\newenvironment{specHead}[2]%
 {\vspace{20pt}\hrule\vspace{10pt}%
  \phantomsection\label{#1}\markright{#2}%

  \pdfbookmark[2]{#2}{#1}%
  \hspace{-0.75in}{\bfseries\fontsize{16pt}{18pt}\selectfont#2}%
  }{}
      \def\TheFullDate{2013-05-15 (revised: 15 May 2013)}
\def\TheID{\makeatother }
\def\TheDate{2013-05-15}
\title{Fault Tolerant Scheduling of Partitioned and Grouped Jobs in Grid Computing (FTPG)}
\author{}\makeatletter 
\makeatletter
\newcommand*{\cleartoleftpage}{%
  \clearpage
    \if@twoside
    \ifodd\c@page
      \hbox{}\newpage
      \if@twocolumn
        \hbox{}\newpage
      \fi
    \fi
  \fi
}
\makeatother
\makeatletter
\thispagestyle{empty}
\markright{\@title}\markboth{\@title}{\@author}
\renewcommand\small{\@setfontsize\small{9pt}{11pt}\abovedisplayskip 8.5\p@ plus3\p@ minus4\p@
\belowdisplayskip \abovedisplayskip
\abovedisplayshortskip \z@ plus2\p@
\belowdisplayshortskip 4\p@ plus2\p@ minus2\p@
\def\@listi{\leftmargin\leftmargini
               \topsep 2\p@ plus1\p@ minus1\p@
               \parsep 2\p@ plus\p@ minus\p@
               \itemsep 1pt}
}
\makeatother
\fvset{frame=single,numberblanklines=false,xleftmargin=5mm,xrightmargin=5mm}
\fancyhf{} 
\setlength{\headheight}{14pt}
\fancyhead[LE]{\bfseries\leftmark} 
\fancyhead[RO]{\bfseries\rightmark} 
\fancyfoot[RO]{}
\fancyfoot[CO]{\thepage}
\fancyfoot[LO]{\TheID}
\fancyfoot[LE]{}
\fancyfoot[CE]{\thepage}
\fancyfoot[RE]{\TheID}
\hypersetup{citebordercolor=0.75 0.75 0.75,linkbordercolor=0.75 0.75 0.75,urlbordercolor=0.75 0.75 0.75,bookmarksnumbered=true}
\fancypagestyle{plain}{\fancyhead{}\renewcommand{\headrulewidth}{0pt}}

\date{}
\usepackage{authblk}

\providecommand{\keywords}[1]
{
\footnotesize
  \textbf{\textit{Index terms---}} #1
}

\usepackage{graphicx,xcolor}
\definecolor{GJBlue}{HTML}{273B81}
\definecolor{GJLightBlue}{HTML}{0A9DD9}
\definecolor{GJMediumGrey}{HTML}{6D6E70}
\definecolor{GJLightGrey}{HTML}{929497} 

\renewenvironment{abstract}{%
   \setlength{\parindent}{0pt}\raggedright
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
   \textcolor{GJBlue}{\large\bfseries\abstractname\space}
}{%   
   \vskip8pt
   \textcolor{GJMediumGrey}{\rule{\textwidth}{2pt}}
   \vskip16pt
}

\usepackage[absolute,overlay]{textpos}

\makeatother 
      \usepackage{lineno}
      \linenumbers
      
\begin{document}

             \author[1]{K.  Srikala}

             \author[2]{S.  Ramachandram}

             \affil[1]{  TutorVista Global Pvt. Ltd}

\renewcommand\Authands{ and }

\date{\small \em Received: 6 April 2013 Accepted: 5 May 2013 Published: 15 May 2013}

\maketitle


\begin{abstract}
        


Computational grids have the potential for solving scientific and large - scale problems using heterogeneous and geographically distributed resources. In addition to the challenges of managing and scheduling resources reliable challenges arise because the grid infrastructure is unreliable. There are two major problems in Scheduling the Grid 1) Efficient Scheduling of jobs, 2) Providing fault tolerance in a reliable manner. Most of the existing strategies do not provide fault tolerance. There are some algorithms which provide fault tolerance but, they do a large amount of redundant computation to provide fault tolerance. This paper addresses this issue and minimizes redundant work by using a group level table of data. This technique is suitable for partitioning and group scheduling of jobs.

\end{abstract}


\keywords{grid computing, grid scheduling, fault tolerance, redundant computation and group result table.}

\begin{textblock*}{18cm}(1cm,1cm) % {block width} (coords) 
\textcolor{GJBlue}{\LARGE Global Journals \LaTeX\ JournalKaleidoscope\texttrademark}
\end{textblock*}

\begin{textblock*}{18cm}(1.4cm,1.5cm) % {block width} (coords) 
\textcolor{GJBlue}{\footnotesize \\ Artificial Intelligence formulated this projection for compatibility purposes from the original article published at Global Journals. However, this technology is currently in beta. \emph{Therefore, kindly ignore odd layouts, missed formulae, text, tables, or figures.}}
\end{textblock*}


\let\tabcellsep& 	 	 		 
\section[{Introduction}]{Introduction}\par
nternet computing has become popular and its popularity is growing with the emerged infrastructure such as web services and computational grids. It is possible to develop applications that support various Internet wide collaborations through seamlessly harnessing appropriate Internet resources. Grid computing is different from distributed computing as grid computing is concerned with large-scale resource sharing, innovative applications and the orientation is high -performance. Therefore, it is important to provide fault tolerant scheduling of jobs.\par
In this paper we propose a fault tolerant scheduling algorithm for partitioning and group scheduling of jobs, i.e., partitioning a Heavy Weight job into a group of Light Weight Jobs and Scheduling Light Weight Jobs as a group.\par
There are three categories of fault tolerant approaches proposed for Grids. They are Job replication, Check pointing and rollback and Adaptive fault tolerance. 
\section[{a) Job Replication}]{a) Job Replication}\par
In Job replication the same job is replicated to be executed on multiple, not dependable resources to replicas could be generated statically or dynamically using the history of failure percentage of a node. 
\section[{b) Check Pointing and Rollback}]{b) Check Pointing and Rollback}\par
In this the state of the running job saved at some fixed points called check points. This state used for recovery of the job in case of a resource failure. 
\section[{c) Adaptive Fault Tolerance}]{c) Adaptive Fault Tolerance}\par
This is the approach where Job replication combines with Check pointing. Here, only one replica will be executing and all other replicas updated periodically, so that if active replica is not available during the recovery of a resource failure we use other replicas.\par
In First two Categories of Fault Tolerance mechanisms there is so much redundant computation involved which leads to high overhead. Though the redundant computation minimized in adaptive fault tolerance communication overhead is still there in this.\par
FTPG provides Fault tolerant scheduling of jobs by maintaining a group table of values for Orphan jobs (Jobs not able to reach Parent Job because of failure of processor at Parent Job). M. Amoon et al \hyperref[b0]{[1]} developed Design of a Fault -Tolerant Scheduling for Grid Computing using Job replication. This uses a fixed number of replicas. Ming Tao et al \hyperref[b1]{[2]} developed a New Replication Strategy for Grid Workflow Applications. They conclude that their strategy optimizes the replication phase in terms of the characteristics of the workflow applications. J.H. Abawahy et al \hyperref[b2]{[3]} developed Fault Tolerant Scheduling Policy for Grid Computing Systems. This uses job replicas. Malarvizhi et al \hyperref[b3]{[4]} developed Fault Tolerant Strategy for Computational Grid Environment.\par
This Scheme uses history of fault occurrence of nodes. August´\textunderscore n Caminero et al \hyperref[b4]{[5]} developed Extending GridSim with architecture for Failure Detection. In all these Schemes the main drawback is redundant computation and some techniques are not able to complete the jobs within the deadlines as a result there is no Quality of Service provided. These are the observations that bring new challenges in designing Fault tolerant Scheduling of jobs, That allows application to continue execution in case of a resource failure. The FTPG addresses all the issues mentioned above.  
\section[{Related Work}]{Related Work}\par
Review of literature reveals that grid environments are more failure prone as the resources may come and go at any time. The most popular fault tolerant mechanism is check pointing. Check pointing is used in Grid computing by systems such as Condor and Cactus. Writing the state of process to a stable storage is the main overhead of this technique. As discussed in the previous section creating greater number of replicas and starting them altogether causes Overhead because of redundant computation.\par
FTPG is different from other fault-tolerance algorithms. This technique is suitable for partitioned and grouped gridlets. That is Heavy weight gridlets are partitioned into a group of Light weight gridlets and Light weight gridlets are scheduled as a group.\par
FTPG based on redoing work lost in crashes. FTPG eliminates the common problem of most fault tolerant algorithms that is redundant computation done by a live processor as a result of crash of its parent processor. This happens in case of Orphan gridlets. Therefore, the Overhead in FTPG is very less. In most of the existing fault tolerant algorithms the processor which has finished working of an Orphan gridlet must discard the result of this gridlet because it does not know where to return that result. The main objectives of FTPG technique are\par
? Reduce the amount of redundant computations.\par
? Providing Fault tolerant service within deadlines imposed by the user.\par
III. 
\section[{Fault Tolerant Scheduling Algorithm}]{Fault Tolerant Scheduling Algorithm}\par
In this section the fault tolerant scheduling algorithm for a group of light weight jobs presented and shown in Figure \hyperref[fig_2]{1}.\par
IV. 
\section[{Process}]{Process}\par
FTPG is suitable for Scheduling a group of light weight jobs. That is when user submits a Heavy Weight Job that is partitioned into Light Weight Jobs and these Light Weight Jobs are scheduled as a group. Or if the user generates Light Weight Jobs they are scheduled as a group. FTPG is based on storing a table of values for the Orphan Jobs. Suppose that a grouped job is sent for execution. All the members of a group has access to group result table designed for this group. This table is used during the crash recovery procedure for storing/reusing the Partial results of Orphan job. (A job/gridlet becomes Orphan when it is not able to send its result back to the parent job.) . Each job can be identified by using its group id, job id and other parameters. When the light weight job's processor is not able to locate its grouped job processor each of the light weight gridlet becomes an orphan and its results are stored in group result table. This table is replicated on all the processors of the group members. The replicas of the table do not have to be strongly consistent because if the processor is not able to find a job it can be recomputed quickly since we are using Light weight jobs here. So updates of the table are propagated asynchronously (for ex: after a fixed amount of time). Since the table stores only Orphan jobs, number of jobs stored is very less. Therefore, the overhead by using the table is very less.\par
With the use of a group table we are storing only the results of finished jobs. They are very easy to store at the same time redundant computation exists only for partially executed light weight jobs. Though this computation is redundant as the gridlet is light weight gridlet it can be computed very quickly and it is possible to finish the jobs within the deadlines imposed by the user.\par
Figure  {\ref 2} and Figure  {\ref 3} demonstrates an example of before the crash and after the crash of group level processor GJ2. The crash recovery procedure for a live processor  Replicas of the table are maintained at each of the processor of Light weight jobs in a group. Update propagation is Asynchronous, The replica's need not be strongly consistent because all the jobs are light weight jobs , So if the finished job's entry is not found in a table it can be computed again in a short period. 
\section[{Global Journal of Computer Science and Technology}]{Global Journal of Computer Science and Technology}\par
In this technique very less amount of redundant computation is there after a crash and adds very little overhead. This Technique is suitable where the jobs are partitioned and a grouped job is sent for execution. In this way redundant computation is minimized that is present in other schemes like check pointing and job replication.\par
V. 
\section[{Simulation Environment and Results}]{Simulation Environment and Results}\par
The Algorithms for comparison (Check pointing (CP),Fixed number of job replicas (4 replicas) FJR (4),Adopted job replication AJR, and fault tolerant Scheduling of Partitioned and grouped jobs FTPG ) are implemented on a machine based on Pentium 1.6GHz with 120GB HDD and RAM of 1GB on Microsoft Windows XP. This experiment is carried out on a simulated grid environment provided by Gridsim.\par
The Simulation environment consists of 6 resources. These 6 resources have 25 PE's in total having different processing capabilities in terms of Millions of Instructions per Second (MIPS).Further it is assumed that there are 8 users with 12 to 30 jobs.\par
FTPG is compared with CP, JR (4) and AJR and the results are recorded on graphs.\par
The parameters used for performance comparison are explained below. Fault-tolerant service describes a technique that is used in case of a processor failure, a backup component or procedure can immediately take its place with no loss of data.\par
The following are the graphs drawn for comparison.\par
Figure4 shows the number of gridlets completed within the deadlines when 20\% faults are injected. We can see that a good percentage of gridlets are completed by using FTPG when compared to AJR, FJR (4) and CP. As the deadline is increased number of jobs completed is also increased. Where as it is not true in case of CP and FJR (4). When the Fixed number of replicas is used as the number of replicas increases the number of jobs executed will be less because of the less availability of resources.\par
FTPG reduces resource wastage and increases user benefit.  The number of gridlets and their execution time is plotted in the graph as shown in Figure \hyperref[fig_7]{5}. These values are measured when 30\% of the processors/resources are failed. It can be observed that as the number of gridlets is increased there is a very little increase in the execution time by using FTPG whereas in the other techniques AJR, FJR (4) and CP as the gridlets are increased their execution time increases drastically. The number of redundant computations when 30\% of the resources failed is measured using CP, AJR, FJR (4) and FTPG and recorded on a pie chart. The results are recorded in figure 6. Figure 6 demonstrates that by using FTPG number of redundant computations were very less in percentage. This improves resource owner benefit by utilizing the resources properly. Therefore, it is good to use FTPG for fault tolerant Scheduling.  
\section[{Conclusions and Future Work}]{Conclusions and Future Work}\par
The FTPG algorithm provides QoS to the user at a good level of acceptance. It uses very less storage for Group Result Table and redundant computations are greatly reduced. The Overhead in this technique is very less.\par
This technique improves user benefit by providing Quality of Service and improves resource owner benefit by minimizing the wastage of resources. This technique can be extended to include network failure, data and service resource failures.\begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-2.png}
\caption{\label{fig_0}B}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-3.png}
\caption{\label{fig_1}VolumeB}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-4.png}
\caption{\label{fig_2}Figure 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{23}\includegraphics[]{image-5.png}
\caption{\label{fig_3}Figure 2 :Figure 3 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-6.png}
\caption{\label{fig_4}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{4}\includegraphics[]{image-7.png}
\caption{\label{fig_6}Figure 4 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{5}\includegraphics[]{image-8.png}
\caption{\label{fig_7}Figure 5 :}\end{figure}
  			\footnote{© 2013 Global Journals Inc. (US)} 			\footnote{BFault Tolerant Scheduling of Partitioned and Grouped Jobs in Grid Computing(FTPG)   } 		 		\backmatter  			 
\subsection[{Global Journals Inc. (US) Guidelines Handbook}]{Global Journals Inc. (US) Guidelines Handbook}\par
www.GlobalJournals.org			 			  				\begin{bibitemlist}{1}
\bibitem[Sulistio et al.]{b4}\label{b4} 	 		\textit{},  		 			August´\textunderscore N Caminero 		,  		 			Anthony Sulistio 		,  		 			Blanca Caminero 		,  		 			Carmen Carri´on 		,  		 			Rajkumar Buyya 		.  		 	 
\bibitem[Malarvizhi Nandagopal et al. ()]{b3}\label{b3} 	 		\textit{},  		 			" Malarvizhi Nandagopal 		,  		 			Fault 		,  		 			Scheduling Strategy For 		,  		 			Computational 		,  		 			Environment" Malarvizhi Nandagopal 		.  	 	 		\textit{/ International Journal of Engineering Science and Technology}  		2010. 2  (9)  p. .  	 
\bibitem[Tao et al. ()]{b1}\label{b1} 	 		‘A New Replication Scheduling Strategy for Grid workflow Applications’.  		 			Ming Tao 		,  		 			Shoubin Dong 		,  		 			Kejing He 		.  	 	 		\textit{Sixth Annual China Grid Conference},  				2011. IEEE@Computer Society.  	 
\bibitem[Amoon ()]{b0}\label{b0} 	 		‘Design of a fault tolerant Scheduling system for Grid Computing’.  		 			M Amoon 		.  		 \xref{http://dx.doi.org/IEEEDOI10.1109/ICNDC.2011.29}{IEEEDOI10.1109/ICNDC.2011.29}.  	 	 		\textit{IEEE Computer Society}  		2011. 2011.  	 
\bibitem[Abawajy ()]{b2}\label{b2} 	 		‘Fault-Tolerant Scheduling Policy for Grid Computing Systems’.  		 			J H Abawajy 		.  	 	 		\textit{Proceedings of the 18th International Parallel and Distributed Processing Symposium (IPDPS'04},  				 (the 18th International Parallel and Distributed Processing Symposium (IPDPS'04)  		2004. IEEE.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
