#name of the .xml file which contains all the transaction definitions.
config_file_name=input.xml

#name of the file which contains the CBMG.
cbmg_file_name=cbmg.txt

#obsolete. 
log_file_name=/tmp/autoProfMaster.log

#port on which master listens for communication from the profilers.
master_port=20202

#approximated value of infinity.
infinity=9999999

#duration after which AutoPerf checks if sufficient no. of transactions have been executed since the last time this check was performed, so that termination criteria can be checked. 
inter_profile_request_time=1001

#load level below which load level is varied sequentially in steps. Above this, load level is varied by applying the binary algorithm discussed in report.
max_seq_var_count=0

#warmup window size during profiling a single transaction
warmup_window_size=5

#when execution count is determined automatically, lower and upper bound on it's value.
lower_bound_on_transaction_execution_count=151
upper_bound_on_transaction_execution_count=2002


#percentage error allowed in the predicted throughput value (when using the binary algorithm)
max_seq_var_threshold=15

#the predicted value of M* is multiplied by this for slight over estimation and binary algorithm is applied in that range.
mstar_lower_bound_multiplier=1.6
#the over-estimated value of M* is multiplied by this, and capacity analysis is performed within the previously over-estimated M* and this new M*. Load level however is varied in seq steps.
mstar_upper_bound_multiplier=1

#window size used for execution count stabilisation detection (at each load level)
avg_execution_count_window_size=9
#percentage deviation allowed in each of the values in the window from the avg of the values in the window.
percentage_error_allowed_in_avg_service_time_observed=20
#criteria for detecting if execution count is sufficient is applied after every 'inter_service_time_measurement_execution_count * load level' increase in the value of execution count
inter_service_time_measurement_execution_count=15
#if observed service demand at a particular server-process is 0 even after the foll. no. of transactions, then execution count automation criteria is not applied further for that process.
maximum_execution_count_when_service_demand_zero=301


#window size used for throughput stabilisation detection (at each load level). The same window is also used for warmup detection in capacity analysis mode.
throughput_window_size=9
#percentage deviation allowed in each of the values in the window from the avg of the values in the window.
percentage_error_allowed_in_throughput_observed=10
#criteria for detecting if throughput has stabilised is applied after every 'inter_service_time_measurement_execution_count * load level' increase in the value of execution count
inter_throughput_measurement_execution_count=10

#if percentage error in 2 successive warmup windows falls below this, we say server has warmed up.
warmup_window_difference_threshold=30

#if percentage timeouts increase beyond this, we stop.
percentage_time_outs_allowed=70
#the above check is made after foll. no. of transactions have been executed.
check_for_percentage_time_outs_after=71








