\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={Performance Test Automation with Distributed Database Systems},
 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{Performance Test Automation with Distributed Database Systems}
\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]{Mungamuru  Nirmala}

             \author[2]{Dr. R. Mahammad  Shafi}

             \affil[1]{  Ministry of Education - NBHE}

\renewcommand\Authands{ and }

\date{\small \em Received: 14 April 2012 Accepted: 4 May 2012 Published: 15 May 2012}

\maketitle


\begin{abstract}
        


Our previous research paper ?A Focus on Testing Issues in Distributed Database Systems' led us to a conclusion that Distributed Database Systems supports many good engineering practices but there is still place for refinements. A Distributed Database (DDB) is formed by a collection of multiple databases logically inter-related in a Computer Network. Apart from managing a plethora of complicated tasks, database management systems also need to be efficient in terms of concurrency, reliability, fault-tolerance and performance. As there has been a paradigm shift from centralized databases to Distributed databases, any testing process, when used in DDB correlates a series of stages for the construction of a DDB project right from the scratch and is employed in homogeneous systems. In this paper, an attempt is made to describe the establishment of Performance Testing with DDB systems. It focuses on the need for maintaining performance and some techniques to achieve performance in DDB systems. Three sample web based systems are tested by using TestMaker, one of the open source software, in order to highlight the helpful role of performance in the context of testing. The strengths and weaknesses of chosen performance testing tools viz., TestMaker, OpenSTA, and httperf are discussed.

\end{abstract}


\keywords{distributed database system, testmaker, openSTA, httperf, performance testing, TPS.}

\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
DDB is formed by a collection of multiple databases logically inter-related in a computer network \hyperref[b2]{[4]}. In a distributed database, the network must allow users to share the data as transparently as possible, yet must allow each node to operate autonomously, especially when network linkages are broken or specific nodes fail. The transparences provided by a DDBMS can be understood as the high level semantic separation of the details inherent to the physical implementation of a DDB. The focus is to provide data independency in a distributed environment.\par
This way, the user sees only one logically integrated image of the DDB as if it were not distributed. Performance evaluation of database systems is an important concern. However, easier said than done, performance evaluation of database system is a non-rivial activity, made more complicated by the existence of different flavors of database systems fine tuned for serving specific requirements. However performance analysts try to identify certain key aspects generally desired of all database systems and try to define benchmarks for them.  
\section[{Overview of performance testing in ddb systems}]{Overview of performance testing in ddb systems}\par
Distributed applications have traditionally been designed as systems whose data and processing capabilities reside on multiple platforms, each performing an assigned function within a known and controlled framework contained in the enterprise. Even if the testing tools were capable of debugging all types of software components, most do not provide a single monitoring view that can span multiple platforms. Therefore, developers must jump between several testing/monitoring sessions across the distributed platforms and interpret the cross-platform gap as best they can. Testing distributed applications is exponentially more difficult than testing standalone applications.\par
Neuman \hyperref[b1]{[2]} categorizes three different dimensions used to measure the Performance of a system, viz., the size of the system, geographical performance, and administrative performance. These measurements ensure that although the users and resources may lie far apart, it is still easy to manage.\par
Performance testing provides the information regarding whether the system can still function in a fastA ( D D D D ) B\par
manner under heavy load. This information assists the IT manager to decide about the inclusion of additional servers. Tanenbaum and Steen \hyperref[b3]{[5]} discussed a number of issues caused by performance. Centralized services, data, and algorithms can become problematic when the number of users increases. Although having a single server to serve a large number of users is not a good idea, adding additional servers to increase the system performance is also not practical in some situations. For example, the information on the server is highly confidential, such as information about bank accounts; adding additional servers create more chances for security attacks.\par
Another issue is geographical performance which also slows down the communication between clients and server. There are some techniques that can help to maintain and improve performance of distributed database systems. The most common technique is replication which adds more and faster processors as well as design components to be scalable \hyperref[b4]{[6]}. Several copies of the same server are made available, the requests are sent to the servers based on their physical location, the loads of the server, or can be sent randomly. Consistency should be taken into consideration when this technique is used. It is to ensure that users can only view the up-todate information and the information appears the same to all users. This technique is not suitable when handling sensitive data, which was mentioned in the previous section.\par
Neuman proposed another technique which is known as distribution \hyperref[b3]{[5]}. Distribution allows a component to be split into smaller parts which can be spread across the system. For instance, a name space is divided into different parts and a part of the naming database is assigned to different servers. Hence, it reduces the number of queries and updates to be processed; also each request is handled faster since the size of the database is smaller. Caching technique is also introduced by Neuman which allow the result to be remembered, thus, additional requests for the same information can be reduced.\par
According to Tanenbaum and Steen, hiding communication latencies technique can be used to enhance the performance of a system \hyperref[b3]{[5]}. That is to say, after the client sends the request, the client continues to do other tasks rather than wait for the response from the server. When the response arrives, the application is interrupted to complete the previous task. 
\section[{III.}]{III.} 
\section[{Testing the performance of sample web based systems}]{Testing the performance of sample web based systems}\par
Web databases serve the back-ends of Web-Servers. Web databases are the classic examples of high load, high performance database systems. The OLC Assets, DCRR and Employee Directory are web based systems. These three systems are chosen as samples for the performance test which is to test how each server reacts when there is an increase in number of users. These tests aim to highlight the role of Performance testing in analyzing system performance.\par
These tests also explain how performance testing can assist testers in making important decisions such as whether the current server(s) are able to serve an increase in the number of concurrent users, or whether additional servers should be implemented in order to handle a high volume of users. 
\section[{a) OLC Assets}]{a) OLC Assets}\par
Otago Language Centre receives a number of new items every day to facilitate students in studying English  {\ref [3]}. These items can be library books, hardware, software, TVs, desks, chairs, etc., whose details are stored in the Center's database for future maintenance. OLC Assets System is a web based system that grants user's access to enter details of each item into the database by completing a simple form. The performance of the system is tested under the situation where there are multiple users who have entered a number of items into the database. Figure \hyperref[fig_1]{2} illustrates the scalability index and XSTest performance index in the context of virtual users and TPS. b) DCRR A web based system that provides access to the users to search for a particular restaurant, comment about a restaurant via an electronic evaluation form, and to add a new restaurant into the database. Figure  {\ref 3} shows two main interfaces of the DCRR system. A number of virtual users accessing the system to add a new restaurant are taken as the scenario for this performance testing. c) Employee Directory This web based system allows users to search for a particular employee and view the details of that employee. Two main interfaces of the system are shown in Figure \hyperref[fig_2]{4}. Performance testing is conducted in the situation where there are an increasing number of users searching for a particular employee.\par
IV. 
\section[{TEST RESULTS and discussion}]{TEST RESULTS and discussion}\par
The three systems are tested using a range of concurrent virtual users (2 -500) in one minute. Because of the limited resources, the maximum number of virtual users was set to 500. The output graphs (Figure \hyperref[fig_2]{2, 3,  and 4}) which starts from 25 virtual users are redrawn based on the original graphs because as they do not show the ratio between number of virtual users appropriately. The original graphs are generated by TestMaker, one of the open source software that supports performance testing.\par
Each graph describes the number of successful transactions per second (TPS) versus the number of( D D D D ) B 2012 
\section[{Year}]{Year}\par
Performance Test Automation with Distributed Database Systems virtual users. The term "transactions per second" is defined as the number of pages per second a server can generate. It can be seen from the graph that as the number of users rises, the number of transactions per second gradually increases.\par
This indication shows that the server is still able to handle a large amount of concurrent requests. On the other hand, if the number of transactions per second drops as the number of users increases, which indicates that there is a concurrency problem and hence leading to performance problem. Although the results generated verify that the servers are still able to manage a large amount of concurrent requests; it is believed that when the number of users keeps growing, the server will fail to handle these requests at some point. Figure \hyperref[fig_1]{2} illustrates the OLC Assets System -XSTest Performance Index, Figure  {\ref 3} indicates the DCRR system performance index and Figure \hyperref[fig_2]{4} shows the Employee Directory system performance index.    
\section[{Performance testing tools}]{Performance testing tools}\par
The performance testing helps in providing valuable information about the system"s performance led to the development of number of performance testing tools. This section examines the strengths and weaknesses of three open source performance testing tools; viz., TestMaker, OpenSTA, and httperf. 
\section[{a) TestMaker}]{a) TestMaker}\par
It is a comprehensive testing framework that is used for performance, functionality, and load testing. A variety of test cases can be generated to perform thorough testing. TestMaker can support the Open Internet Protocols (HTTP, HTTPS, SOAP, XML-RPC, SMTP, POP3, IMAP, etc.). This software allows testers to create a number of virtual users and with the support from Test Network, testers can generate up to 10,000 or more concurrent test agents. TestMaker generates a clear output graph that represents the performance of the server based on the number of transactions per second versus the number of virtual users.\par
Apart from the strengths that are provided in the open source version, the commercial version offers some additional features such as the XSTest Pro that delivers performance index which helps to identify performance problems for capacity planning. Service Monitor System can send notifications via emails to notify, when a service fails or responds too slowly. Reports (charts and graphs) are generated to show the Performance index, result timing distribution, and performance timing by operation. This is an extremely useful feature since it is the quickest way to analyze the performance of the system. Another feature called Test Network, allows testers to generate a large amount of virtual users to test a specific web service.\par
On the contrary, TestMaker does have some weaknesses. Graphs are generated based on the number of transactions per second. In doing so, it assumes that all transactions are the same, even though some transactions may be long or short or complex. There is a possibility that a complex transaction may take shorter time to complete and this is not reflected on the graph. In addition, test cases should be performed more than one time to get the correct outputs. 
\section[{b) OpenSTA}]{b) OpenSTA}\par
It is a completely free framework for testing the performance of Web Application Environments (WAEs). It is designed to create and run HTTP/S load tests in order to assess the performance of WAEs. OpenSTA provides a very simple GUI to create a new test, new collector, and a new script.\par
A new script is written in Script Control Language (SCL) and created by recording a list of activities that are carried out by the users. According to OpenSTA documentation \hyperref[b3]{[5]}, the process of creating collectors involves "deciding from which host computers or other devices performance data has to be collected and the type of data to collect".\par
After scripts and collectors are created, they are added into a test. Each test can be edited and controlled by using a number of features that are provided by the Graphical User Interface. These features include description about the test, start time, number of iterations, host name, number of virtual users, duration of the test, delay between each iteration, etc. Test can be monitored during execution and the result is displayed in graph when the test completes. Graphs can be customized to improve the presentation of data.\par
Finally, Easy to follow documentation along with online help and commercial support are provided by the vendors. One of the weaknesses is that OpenSTA can only support HTTP and HTTPS protocols; it can only run on Windows OS. Another difficulty is that testers have to understand the SCL language. 
\section[{c) httperf}]{c) httperf}\par
It is a tool for measuring web server performance. A test is executed at the command line by specifying hostname, port, page address, rate, number of connections, and timeout. Timeout features help testers to define the number of seconds that each client is willing to wait for the response from the server. When a test completes, the result is generated in the form of plain text. Mosberger and Jin explained that the output consists of six groups \hyperref[b0]{[1]}. These groups covers the overall results, results pertaining to the TCP connections; requests that were sent; results for the replies that were received; CPU and network utilization figures and a summary of the errors that occurred. A performance graph is generated by httperf to illustrate the server performance. httperf has some weaknesses such as it only supports the HTTP protocol and can only run on a Linux OS. In addition, Mosberger and Jin point out that the testers have to start httperf on each client machine collect and summarize each clientresult. They also suppose that a single command line that can control multiple clients could help in improving httperf.  
\section[{TOOLS FEATURES}]{TOOLS FEATURES} 
\section[{Conclusion}]{Conclusion}\par
A distributed database is not stored in its entirety at a single physical location. Instead, it is spread across a network of computers that are geographically dispersed and connected via communications links. A key objective for a distributed system is that it looks like a centralized system to the user. The user should not need to know where a piece of data is stored physically. Testing the performance of such an environment is really a typical task. Existing web-application performance-testing tools offer a broad variety of functionality. However, none of them combines all the functionality we expected to use in our projects. In an ideal world, everything works perfectly when the test is run. In reality, first runs often show problems in server configuration or in application itself. An effort has been made to test the performance of DDB systems like OLC Assets, DCRR and Employee Directory using some open source performance testing tools like TestMaker, OpenSTA and httperf.\begin{figure}[htbp]
\noindent\textbf{1}\includegraphics[]{image-2.png}
\caption{\label{fig_0}Fig. 1 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{2}\includegraphics[]{image-3.png}
\caption{\label{fig_1}Fig. 2 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{4}\includegraphics[]{image-4.png}
\caption{\label{fig_2}Fig. 4 :}\end{figure}
 \begin{figure}[htbp]
\noindent\textbf{1} \par 
\begin{longtable}{P{0.33260869565217394\textwidth}P{0.25869565217391305\textwidth}P{0.25869565217391305\textwidth}}
TestMaker\tabcellsep OpenSTA\tabcellsep httperf\end{longtable} \par
 
\caption{\label{tab_2}Table 1 :}\end{figure}
 			\footnote{© 2012 Global Journals Inc. (US)} 		 		\backmatter  			  				\begin{bibitemlist}{1}
\bibitem[Stonebraker et al. ()]{b7}\label{b7} 	 		‘A Guide to Performance Evaluation of Database Systems, Superintendent of Documents’.  		 			Michael Stonebraker 		,  		 			Dorothy ; With Moore 		,  		 			-S Yao 		,  		 			Alan R Bing 		,  		 			Hevner 		.  	 	 		\textit{Government Printing Office}  		1996. 1984. Morgan Kaufmann Publishers. 20402  (10) .  	 	 (Object-Relational DBMSs: The Next Great Wave) 
\bibitem[Boral et al. (1984)]{b8}\label{b8} 	 		‘A methodology for database system performance evaluation’.  		 			Haran Boral 		,  		 			J David 		,  		 			Dewitt 		.  	 	 		\textit{ACM SIGMOD Record}  		June 1984. 14  (2) .  	 
\bibitem[Codd ()]{b6}\label{b6} 	 		‘A Relational Model of Data for Large Shared Data Banks’.  		 			E F Codd 		.  	 	 		\textit{Communications of the ACM}  		1970. 13  (6)  p. .  	 
\bibitem[Ceri and Pelagatti ()]{b11}\label{b11} 	 		 			Stefano Ceri 		,  		 			Giuseppe Pelagatti 		.  		\textit{Distributed Databases: Principles and Systems},  				 (New York, McGrawHill)  		1984.  	 
\bibitem[Emmerich ()]{b4}\label{b4} 	 		\textit{Distributed System Principles},  		 			W Emmerich 		.  		1997.  		 			UK: University College London 		 	 
\bibitem[Tanenbaum and Steen]{b3}\label{b3} 	 		\textit{Distributed Systems -Principles and Paradigms},  		 			A S Tanenbaum 		,  		 			M V Steen 		.  		America: Prentice-Hall.  	 
\bibitem[Mosberger and Jin]{b0}\label{b0} 	 		\textit{httperf -A Tool for Measuring Web Server Performance},  		 			D Mosberger 		,  		 			T Jin 		.  		 	 
\bibitem[Shafi]{b2}\label{b2} 	 		‘Kavitha -A Framework for Designing and Testing a Distributed Database System’.  		 			R Shafi 		,  		 			DrB 		.  	 	 		\textit{Proceedings of AMCM-2011},  				 (AMCM-2011)  		 	 
\bibitem[Zhu and Lu ()]{b5}\label{b5} 	 		‘Performance analysis of Web Database systems’.  		 			Yuanling Zhu 		,  		 			Kevin Lu 		.  	 	 		\textit{LNCS}  		Volume1873/2000. 2000. p. .  	 
\bibitem[Peter et al. ()]{b9}\label{b9} 	 		\textit{Performance Evaluation of a Distributed Enterprise Data Mining System},  		 			G Peter 		,  		 			Catalina M Harrison 		,  		 			Llado 		.  		2000. 2000. p. .  	 
\bibitem[Neuman]{b1}\label{b1} 	 		\textit{Scale in Distributed Systems. Readings in Distributed Computing Systems},  		 			B C Neuman 		.  		IEEE Computer Society Press.  	 
\bibitem[Date ()]{b10}\label{b10} 	 		\textit{What is a Distributed Database System?},  		 			C J Date 		.  		1990. reading, Mass: Addision-Wesley.  	 	 (in Relational Database writings 1985-1989) 
\end{bibitemlist}
 			 		 	 
\end{document}