\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={Analysis and Strategy for the Performance Testing in Cloud Computing},
 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{2012-05-15 (revised: 15 May 2012)}
\def\TheID{\makeatother }
\def\TheDate{2012-05-15}
\title{Analysis and Strategy for the Performance Testing in Cloud Computing}
\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]{Dr. Eljona  Proko}

             \author[2]{Ilia  Ninka}

             \affil[1]{  Vlora University}

\renewcommand\Authands{ and }

\date{\small \em Received: 10 April 2012 Accepted: 30 April 2012 Published: 15 May 2012}

\maketitle


\begin{abstract}
        


The aim of this study is the analysis and presentation of some ideas on performance testing in Cloud Computing. Performance is an important factor in testing a web application. Performance testing in cloud computing is different from that of traditional applications. Our research methodology in this article includes an overview of existing works on testing performance in Cloud Computing, focusing on discussion that the traditional benchmarks are not sufficient to analyze performance testing in Cloud Computing. In this study we are focused mainly on analysis performance metrics in Cloud Computing, based on their characteristics such as elasticity, scalability, pay-per-use and fault tolerance, and then we discuss why needed new strategies for performance testing in Cloud Computing and creation of new benchmarks. From this study we conclude that the performance testing and evaluation should be performed using new models testing, which are created according to Cloud Computing characteristics and metrics.

\end{abstract}


\keywords{Cloud computing, characteristics, performance, testing, benchmarks, strategy.}

\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
odern computer system is becoming more complex and this depends on the network technologies on the internet. Performance testing \hyperref[b0]{[1]} intended to measure system throughput and latency with varying number of concurrent users, over extended periods of times, and with different load profiles. Performance testing in cloud computing is different from that of traditional applications. The traditional performance testing focused on the performance metrics for applications that are under a particular workload for a fixed configuration. Cloud test need to measure the performance metrics related to the workloads that run in a distributed fashion on multiple virtual and real machines. The growth of cloud computing created a demand for new strategy that can measure the performance characteristics of cloud applications.\par
This paper begins by describing Cloud Computing definition. Section III describes cloud computing characteristics. Section IV discusses traditional benchmarks problems regarding performance testing in Cloud Computing. Section V discusses ideas for new strategies and creation of new models in testing cloud computing. In Section V we conclude this study. 
\section[{II.}]{II.} 
\section[{Cloud computing}]{Cloud computing}\par
Cloud Computing is a model that offers the vision of a virtually infinite pool of computing, storage and networking resources where applications can be scalable deployed \hyperref[b1]{[2]}. Fig. \hyperref[fig_1]{1} illustrates cloud computing scheme. This cloud model promotes availability and is composed of five essential characteristics, four deployment models, and three service models \hyperref[b2]{[3]}. a) Essential Characteristics i. 
\section[{On-demand self-service based usage model}]{On-demand self-service based usage model}\par
A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service's provider.\par
ii. 
\section[{Multi Tenancy with resource pooling}]{Multi Tenancy with resource pooling}\par
The provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. There is a sense of location independence in that the customer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter). Examples of resources include storage, processing, memory, network bandwidth, and virtual machines.\par
iii. 
\section[{Broad network access for distributed resources}]{Broad network access for distributed resources}\par
Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs). iv. 
\section[{Elasticity to provision capabilities quickly}]{Elasticity to provision capabilities quickly}\par
Capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time. capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts).\par
Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service. b) Deployment Models i. 
\section[{Private cloud}]{Private cloud}\par
The cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on premise or off premise.\par
ii. 
\section[{Public cloud}]{Public cloud}\par
The cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.\par
iii. 
\section[{Community cloud}]{Community cloud}\par
The cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on premise or off premise. iv. 
\section[{Hybrid cloud}]{Hybrid cloud}\par
The cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds) c) Service Models i. 
\section[{Cloud Software as a Service (SaaS)}]{Cloud Software as a Service (SaaS)}\par
The capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based email). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.\par
ii. 
\section[{Cloud Platform as a Service (PaaS)}]{Cloud Platform as a Service (PaaS)}\par
The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.\par
iii.\par
Cloud Infrastructure as a Service (IaaS)\par
The capability provided to the consumer is to provide processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating system; storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).  
\section[{Cloud computing characteristics}]{Cloud computing characteristics}\par
A metric is used to measure and understand the behavior of software. Cloud metrics can be used to measure the behavior of cloud which utilizes the resources from the computers as a collective virtual computer, where the applications can run independently from particular computer or server configurations \hyperref[b8]{[10]}. Cloud delivers its services through internet and provides the full user functionality of a software application by the web sites which provide Software as a Service. Dynamic web sites provide regularly changing information to users and utilize dynamically generated pages and maintain data for display in a database \hyperref[b7]{[9]}. Cloud uses the dynamic web sites to deliver the web applications on demand. Cloud metrics should follow some characteristics which help to evaluate cloud on each and every parameter which is necessary for a good quality cloud, so that a client can rely on it to choose the best cloud.\par
The main advantages of cloud computing are scalability, pay-per-use and fault-tolerance \hyperref[b3]{[4]}. a) Elasticity [8] is one of the major factors for the success of the cloud as an IT infrastructure. For a DBMS deployed on a pay-per-use cloud infrastructure, an added goal is to optimize the system's operating cost. Elasticity, i.e. the ability to deal with load variations by adding more resources during high load or consolidating the tenants to fewer nodes when the load decreases, all in a live system without service disruption, is therefore critical for these systems. Even though( D D D D ) B\par
elasticity is often associated with the scale of the system, a subtle difference exists between elasticity and scalability when used to express a system's behavior. b) Scalability is a desirable property of a system, which indicates its ability to either handle growing amounts of work in a graceful manner or its ability to improve throughput when additional resources (typically hardware) are added. A system, whose performance improves after adding hardware, proportionally to the capacity added, is said to be a scalable system. c) Reliability is the probability that a product or part will operate properly for a specified period of time (design life) under the design operating conditions (such as temperature, volt, etc.) without failure \hyperref[b5]{[6]}. The outcome of the measurement process is reproducible that is similar to results over time for some different inputs and across many different situations. Cloud gets many requests simultaneously and will also give the similar results for some requests in a period of time so clouds have to be reliable. d) Availability Cloud Services should be available maximum time  {\ref [7]}. The on demand, elastic, scalable, and customizable nature of the cloud must be considered when deploying cloud architectures. Many different clients might be accessing the same back-end applications, and many provider are providing the cloud services has the expectation that only their application will be properly delivered to users. In cloud computing it is essentially required to gather the information instantly without making a user to wait and the gathered information should be related to each other. e) Cost Cloud Computing allows an organization to pay by the hour of computing resources, potentially leading to cost savings even if the hourly rate to rent a machine from a cloud provider is higher than the rate to own one. This is essentially preferable when demand for a service that varies over time. f) Fault Tolerance is one of the key issues of cloud computing. There are many fault tolerance techniques in parallel computing \hyperref[b9]{[11]}. Fault tolerance is concerned with all the techniques necessary to enable a system to tolerate software faults. These software faults Fig.  {\ref 2}: Some of the cloud computing characteristics IV. 
\section[{Traditional benchmarks are not sufficient to analyze performance testing in cloud computing}]{Traditional benchmarks are not sufficient to analyze performance testing in cloud computing}\par
The goal of benchmarking a software system is to evaluate its average performance under a particular workload. TPC-W [14] has been designed for transactional database systems. Cloud systems usually do not offers strong consistency constraints because most web-based applications only require lower levels of consistency. As a consequence existing TPC-W implementations for the cloud are not conforming to the specification. The primary metric used by the TPC-W \hyperref[b11]{[13]} is WIPS that the system under test can handle. By scaling the number of emulated browsers, the number of requests and the load on the system can be increased. WIPS is useful in the context of a static system it is not for adaptable and scalable systems. The second metric of the TPC-W is \$/WIPS, is based on the total cost of ownership of the system under test including software, hardware, maintenance and administration expenses. These overall costs are then divided by the maximum number of WIPS to calculate the \$/WIPS. In the context of cloud computing does not exists maximum number of WIPS. Thus, there exists no fixed load for which the overall cost can be calculated. TPC-W became outdated in front the evolution of web applications and does not reflect modern access-paths. TPC-W benchmark has not the adequate metrics for measuring the characteristics of cloud systems, such as pay-per use scalability and fault tolerance.\par
V. 
\section[{Idea for testing performance in cloud computing}]{Idea for testing performance in cloud computing}\par
Performance is generally tied to an application's capabilities within the cloud infrastructure itself. Testing is a periodic activity and requires new environments to be set up for each project \hyperref[b10]{[12]}. Web applications must be tested for multiple operating systems and updates, multiple browser platforms and versions, different types of hardware and a large number of concurrent users to understand their performance in real-time \hyperref[b4]{[5]}. Cloud Computing is growing at a rapid pace. With the advent of this technology, there is bound to be an increase in demand for Cloud Testing. New cloud test should be based on an e-commerce scenario (i.e., a web-shop) and define web interactions as test drivers. Thus, the test should allow the evaluation of the complete application stack. A new cloud test should analyze the ability of a dynamic system to adapt to a changing load (including peaks) in terms of scalability and costs. Moreover, another goal is to test to the assumption of infinite scalability of an application in the cloud. Cloud providers often replicate data over different data centers for availability but also performance reasons. In order to get a fair comparison of the test results, the emulated browsers should run in different locations (worldwide). By doing this, we can achieve that the test results are not biased due to the location where the test driver is running. A solution to this problem is to run the test drivers on a cloud infrastructure of a provider which supports location based installations. A new test should comprise web interactions that resemble the access patterns of Web 2.0 like applications. One example is to add web interactions that allow users to write and read reviews of individual products or to add web interactions that allow user communities to exchange the latest news about certain products. Web 2.0 applications often include multimedia content (audio files, video files, pictures) which can be accessed by users. This content produces heavy load on the servers which host that content. Cloud makes it cost-effective for creating separate test regions for system testing. The test strategy should answer what is intended to be achieved by moving testing to the cloud, including cost savings, easy access to infrastructure, reduction in cycle times, etc. The strategy should define the type of tests to be performed in the cloud, the risks associated and the duration of the tests. We need to define the infrastructure requirements necessary for building a test environment by selecting the required testing tools and applications, hardware and software, bandwidth, etc. The next step is selection of a service provider for security, quality, reliability and any discrepancies in the terms and conditions. Executing the test is the critical phase where applications are tested according to the defined test strategy. Monitor and analyze test results is the last step. It is advised that test results be monitored in real-time to understand and react to capacity-or performance-related issues. Also, analyze cloud usage against chargeback costs to understand the financial performance of cloud services. 
\section[{VI.}]{VI.} 
\section[{Conclusion}]{Conclusion}\par
The growth of cloud computing created a demand for benchmarks that can measure the performance characteristics of cloud applications.\par
The traditional performance benchmarking focused on the performance metrics for applications that run on single node systems. Cloud benchmarks need to measure the performance metrics related to the workloads that run in a distributed fashion on multiple virtual and real machines. Metrics are the necessary and important elements for evaluation the quality enabling the identification of a good Cloud Computing. The performance metrics for the distributed workloads need to be defined based on the cloud application characteristics.\begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-2.png}
\caption{\label{fig_0}}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-3.png}
\caption{\label{fig_1}Fig. 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{}\includegraphics[]{image-4.png}
\caption{\label{fig_2}}\end{figure}
 			\footnote{July} 			\footnote{July} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Cognizant]{b10}\label{b10} 	 		\textit{},  		 			Cognizant 		.  		 	 	 (Taking Testing to the Cloud) 
\bibitem[Armbrust ()]{b3}\label{b3} 	 		\textit{Above the clouds: A berkeley view of cloud computing},  		 			M Armbrust 		.  		 UCB/EECS-2009-28.  		2009.  	 	 (Technical Report) 
\bibitem[Singh and Sood (2011)]{b8}\label{b8} 	 		‘Amit Sharma CM-Measurement Facets for Cloud Performance’.  		 			Gurdev Singh 		,  		 			Shanu Sood 		.  	 	 		\textit{International Journal of Computer Applications}  		June 2011. 23  (3)  p. .  	 
\bibitem[Hayes (2008)]{b1}\label{b1} 	 		‘Cloud computing’.  		 			B Hayes 		.  	 	 		\textit{Communications of the ACM}  		Jul. 2008. 51  (7)  p. .  	 
\bibitem[Elasticity in Cloud Computing (2011)]{b6}\label{b6} 	 		\textit{Elasticity in Cloud Computing},  				 (Inria Rhône-Alpes)  		June 23, 2011.  	 	 (Team Sardes) 
\bibitem[Gong et al.]{b9}\label{b9} 	 		\textit{Haitao Chen and Zhenghu Gong The Characteristics of Cloud Computin},  		 			Chunye Gong 		,  		 			Jie Liu 		,  		 			Qiang Zhang 		.  		 	 
\bibitem[Ian Molyneaux -The Art of Application Performance Testing]{b4}\label{b4} 	 		\textit{Ian Molyneaux -The Art of Application Performance Testing},  		 	 
\bibitem[Kareim et al.]{b5}\label{b5} 	 		\textit{Multi-Channel Clustered Web App lication Server" 7},  		 			M Kareim 		,  		 			Ahmed Sobhe 		,  		 			Sameh 		.  		NetPrecept Software Ltd.  	 	 (Making Cloud Service Continuity a Reality) 
\bibitem[Meier ()]{b0}\label{b0} 	 		\textit{Performance Testing Guidance for Web Applications. Microsoft Corporation},  		 			J D Meier 		.  		2007. United States.  	 
\bibitem[Mell]{b2}\label{b2} 	 		‘Timothy Grance The NIST Definition of Cloud Computing’.  		 			Peter Mell 		.  	 	 		\textit{Special Publication}  		p. .  	 
\bibitem[Cleary]{b7}\label{b7} 	 		‘Web Based Development and Functional Size Measurement’.  		 			David Cleary 		.  	 	 		\textit{IFPUG Annual conference}  		 	 
\bibitem[Benchmark Tm W (1 October 18August 23. 2000 14)]{b11}\label{b11} 	 		‘Web Commerce) Specification Version 1.21’.  		 			Tpc Benchmark Tm W 		.  	 	 		Tihamér Levendovszky TPC Benchmark  		1 October 18August 23. 2000 14. Márk Kaszó.  	 
\end{bibitemlist}
 			 		 	 
\end{document}
