Hao, It shouldn't be necessary to reload the DB every run, but it depends on what you are testing. If you are testing app server infrastructure then you want the DB to behave consistently. Every run you make adds data to the DB, at some point, you might find that transaction times to the DB start to increase, or worse, they do but you don't realise. Loading the DB for every run means that you don't have to factor in the state of the DB in order to interpret the results.
Amanda On Tue, Jun 15, 2010 at 12:25 AM, hao zhang <[email protected]>wrote: > Hi, > I found that the percentage of adding person operating is relative > low, and thus the percentage of such error should be even lower. > Besides this, is there any other important reason to reload the database? > Thanks. > > - Hao > > 2010/6/14 Bruno Guimarães Sousa <[email protected]>: > > I imagine that there's a need to reload the database even in your > situation. > > During each run, olio's workload is determined to add new users too. So, > as > > I experienced it, sometimes the user that it tries to add is already in > > database and you receive an error message. > > > > regards, > > -- > > Bruno Guimarães Sousa > > www.ifba.edu.br > > PONTONET - DGTI - IFBA > > Ciência da Computação UFBA > > Registered Linux user #465914 > > > > > > On Mon, Jun 14, 2010 at 3:19 PM, hao zhang <[email protected]> > > wrote: > >> > >> Hi, > >> Can anyone explain why the database and data storage needs to be > >> reloaded before each run? > >> If I have already loaded the database and data storage, say for 10,000 > >> users. Then do I need to reload them again if the following tests have > >> concurrent user less than 100? > >> Thanks. > >> > >> - Hao > > > > >
