Hi Kumar

Why don't you start a new instance for your question and asking it from my 
question instance. 

Just prepare your mail  and send it to sipp users mail group instead of 
replying my mail.

Thanks


Samsung Mobile tarafından gönderildi

<div>-------- Orjinal mesaj --------</div><div>Kimden: kumar uppu 
<kumar94...@gmail.com> </div><div>Tarih:21 10 2014  12:12  (GMT+02:00) 
</div><div>Alıcı: Sakharam Thorat <sakharam.tho...@outlook.com> </div><div>Cc: 
Kaan Dandin <kaan.dan...@gmail.com>,Gunes Kurt <gk...@itu.edu.tr>,"Ibrahim 
Hokelek, (BİLGEM-UEKAE)" <ibrahim.hoke...@tubitak.gov.tr>,sipp-users 
<sipp-users@lists.sourceforge.net> </div><div>Konu: Re: [Sipp-users] 
doReport.pl errors </div><div>
</div>Hi guys 

i want to install fedora 6 in my new hard disk

can any please instruct how to download and install fedora 6 in new hard disk



Thanks
Kumar

On Tue, Oct 21, 2014 at 11:24 AM, Sakharam Thorat <sakharam.tho...@outlook.com> 
wrote:
http://isoredirect.centos.org/centos/6/isos/x86_64/

--- Original Message ---

From: "kumar uppu" <kumar94...@gmail.com>
Sent: October 21, 2014 10:51 AM
To: kaan.dan...@gmail.com
Cc: "Gunes Kurt" <gk...@itu.edu.tr>, "Ibrahim Hokelek, (BİLGEM-UEKAE)" 
<ibrahim.hoke...@tubitak.gov.tr>, sipp-users@lists.sourceforge.net
Subject: Re: [Sipp-users] doReport.pl errors

HI guys,
 
 can any please send a link for downloading fedora 6 

Thanks
Kumar

On Tue, Oct 21, 2014 at 1:16 AM, <kaan.dan...@gmail.com> wrote:
Hi all,
 
I have finished IMS-Bench - OpenSIPS-OpenIMS integration.
 
Now I would like to have reports for the scenario. But I have some problems 
with reports.
 
Below you can find output for doReport.pl , there are some errors.
 
And in the report.html some plots are missing.
 
root@ubuntu:/opt/ims_bench/ims_bench_0# ../scripts/doReport.pl -i ims_bench.xml
Loading data from report.xml
Test Date: 15-Jul-2014 13:25
Test Duration: 197.035
Number of SUTs: 1
Number of Test Systems: 1
Number of steps: 7
File=>CALL_DURATION.dat, Name=>CALL_DURATION, m_id=>3
File=>PX_TRT-PMM1.dat, Name=>PX_TRT-PMM1, m_id=>0
File=>PX_TRT-REG1.dat, Name=>PX_TRT-REG1, m_id=>0
File=>PX_TRT-REG1_ims_reg.dat, Name=>PX_TRT-REG1, m_id=>0, 
scenario_name=>ims_reg , s_id=>2, uid = 0
File=>PX_TRT-REG1_ims_dereg.dat, Name=>PX_TRT-REG1, m_id=>0, 
scenario_name=>ims_dereg , s_id=>3, uid = 0
File=>PX_TRT-REG2.dat, Name=>PX_TRT-REG2, m_id=>1
File=>PX_TRT-REG2_ims_reg.dat, Name=>PX_TRT-REG2, m_id=>1, 
scenario_name=>ims_reg , s_id=>2, uid = 0
File=>PX_TRT-REG2_ims_dereg.dat, Name=>PX_TRT-REG2, m_id=>1, 
scenario_name=>ims_dereg , s_id=>3, uid = 0
File=>PX_TRT-REG4.dat, Name=>PX_TRT-REG4, m_id=>0
File=>PX_TRT-REL1.dat, Name=>PX_TRT-REL1, m_id=>2
File=>PX_TRT-SES1.dat, Name=>PX_TRT-SES1, m_id=>0
File=>PX_TRT-SES2.dat, Name=>PX_TRT-SES2, m_id=>1
File=>PX_TRT-REG2_no_use_case.dat, Name=>PX_TRT-REG2, m_id=>1, 
scenario_name=>ims_reg, s_id=>2, uid = 0
File=>PX_TRT-REG2_no_use_case.dat, Name=>PX_TRT-REG2, m_id=>1, 
scenario_name=>ims_dereg, s_id=>3, uid = 0
File=>PX_TRT-REG1_no_use_case.dat, Name=>PX_TRT-REG1, m_id=>0, 
scenario_name=>ims_reg, s_id=>2, uid = 0
File=>PX_TRT-REG1_no_use_case.dat, Name=>PX_TRT-REG1, m_id=>0, 
scenario_name=>ims_dereg, s_id=>3, uid = 0
8 metrics in total; 1 use cases
2 'per scenario' metrics
4 'per use case' metrics
Now looking at step 0...1...2...
Building Temporary Files from sipp.csv took 0.01 sBuild retransmit from 
sipp.csv took 0.00 sec
Step 0 (run 0) report=0 show_in_tables=1 show_histograms=0
   doc_step=0 over_ihs=0 label="pre-reg"
Step 1 (run 2) report=0 show_in_tables=0 show_histograms=0
   doc_step=0 over_ihs=0 label="step 1"
Step 2 (run 3) report=0 show_in_tables=0 show_histograms=0
   doc_step=0 over_ihs=0 label="step 2"
Step 3 (run 3) report=0 show_in_tables=0 show_histograms=0
   doc_step=0 over_ihs=0 label="step 3"
Step 4 (run 3) report=0 show_in_tables=0 show_histograms=0
   doc_step=0 over_ihs=0 label="step 4"
Step 5 (run 3) report=0 show_in_tables=0 show_histograms=0
   doc_step=0 over_ihs=0 label="step 5"
Step 6 (run 3) report=0 show_in_tables=0 show_histograms=0
   doc_step=0 over_ihs=0 label="step 6"
Failure step will be displayed: runtime changed from 197.035 to 196.098
SAPS  ready to be plotted
 => (SAPS, , ) using SAPS.dat, 2
 
set terminal png small size 1200 , 400
  CPU  ready to be plotted
 => (CPU, , ) using cpumem2_0.csv, 2
 => nothing to plot (Failed to open cpumem2_0.csv)
MEM  ready to be plotted
 => (MEM, , ) using cpumem2_0.csv, 3
 => nothing to plot (Failed to open cpumem2_0.csv)
     ALL-SIPP-CPU  ready to be plotted
      ^
"SAPS-meantime.png.gpl", line 2:  => (ALL-SIPP-CPU, , ) using 
sipp_TS1_cpumem2.csv, 2
unknown or ambiguous terminal type; type just 'set terminal' for a list
 
 => (SAPS, , ) using SAPS.dat, 2
ALL-SIPP-MEM  ready to be plotted
 => (ALL-SIPP-MEM, , ) using sipp_TS1_cpumem2.csv, 3
 => (SAPS, , ) using SAPS.dat, 2
IHS  ready to be plotted
 => (IHS, , ) using IHS.dat, 2
DOC not reached = 1.66666666666667
 => (SAPS, , ) using SAPS.dat, 2
RETRANSMIT  ready to be plotted
 => (RETRANSMIT, , ) using retrans.dat, 2
 => (SAPS, , ) using SAPS.dat, 2
 
set terminal png small size 1200 , 400
             ^
"ALL-SIPP-CPU-normaltime.png.gpl", line 4: unknown or ambiguous terminal type; 
type just 'set terminal' for a list
 

set terminal png small size 1200 , 400
         PX_TRT-REG1  ready to be plotted
    ^
"ALL-SIPP-MEM-normaltime.png.gpl", line 4: unknown or ambiguous terminal type; 
type just 'set terminal' for a list
 
 => (PX_TRT-REG1, , Registration) using PX_TRT-REG1.dat, 2
 
set terminal png small size 1200 , 400
             ^
"IHS-normaltime.png.gpl", line 4: unknown or ambiguous terminal type; type just 
'set terminal' for a list
 

set terminal png small size 1200 , 400
             ^
"RETRANSMIT-normaltime.png.gpl", line 4: unknown or ambiguous terminal type; 
type just 'set terminal' for a list
 
 => use_case Registration not defined in report.xml => using total SAPS instead
 => (SAPS, , Registration) using SAPS.dat, 2
PX_TRT-REG2  ready to be plotted
 => (PX_TRT-REG2, , Registration) using PX_TRT-REG2.dat, 2
 
set terminal png small size 1200 , 400
             ^
"PX_TRT-REG1Registration-meantime.png.gpl", line 4: unknown or ambiguous 
terminal type; type just 'set terminal' for a list
 
 => use_case Registration not defined in report.xml => using total SAPS instead
 => (SAPS, , Registration) using SAPS.dat, 2
RETRANSMIT ims_reg ready to be plotted
 => (RETRANSMIT, ims_reg, Registration) using retrans.dat, 5
 => (SAPS, ims_reg, Registration) using SAPS.dat, 5
 
set terminal png small size 1200 , 400
             ^
"PX_TRT-REG2Registration-meantime.png.gpl", line 4: unknown or ambiguous 
terminal type; type just 'set terminal' for a list
 
PX_TRT-REG1 ims_reg ready to be plotted
 => (PX_TRT-REG1, ims_reg, Registration) using PX_TRT-REG1_ims_reg.dat, 2
 
set terminal png small size 1200 , 400
             ^
"RETRANSMITRegistrationims_reg-normaltime.png.gpl", line 4: unknown or 
ambiguous terminal type; type just 'set terminal' for a list
 
 => (SAPS, ims_reg, Registration) using SAPS.dat, 5
PX_TRT-REG4 ims_rereg ready to be plotted
 => (PX_TRT-REG4, ims_rereg, Registration) using PX_TRT-REG4.dat, 2
 => nothing to plot ()
PX_TRT-REG1 ims_dereg ready to be plotted
 => (PX_TRT-REG1, ims_dereg, Registration) using PX_TRT-REG1_ims_dereg.dat, 2
 => nothing to plot ()
PX_TRT-SES1  ready to be plotted
 => (PX_TRT-SES1, , Calling) using PX_TRT-SES1.dat, 2
 => nothing to plot ()
PX_TRT-SES2  ready to be plotted
 => (PX_TRT-SES2, , Calling) using PX_TRT-SES2.dat, 2
 => nothing to plot ()
PX_TRT-REL1  ready to be plotted
 => (PX_TRT-REL1, , Calling) using PX_TRT-REL1.dat, 2
 
set terminal png small size 1200 , 400
             ^
"PX_TRT-REG1Registrationims_reg-meantime.png.gpl", line 4: unknown or ambiguous 
terminal type; type just 'set terminal' for a list
 
 => use_case Calling not defined in report.xml => using total SAPS instead
 => (SAPS, , Calling) using SAPS.dat, 2
PX_TRT-SES3  ready to be plotted
 => (PX_TRT-SES3, , Calling) using PX_TRT-SES3.dat, 2
 => nothing to plot (Failed to open PX_TRT-SES3.dat)
RETRANSMIT ims_uac ready to be plotted
 => (RETRANSMIT, ims_uac, Calling) using retrans.dat, 3
 
set terminal png small size 1200 , 400
             ^
"PX_TRT-REL1Calling-meantime.png.gpl", line 4: unknown or ambiguous terminal 
type; type just 'set terminal' for a list
 
 => (SAPS, ims_uac, Calling) using SAPS.dat, 3
IHS ims_uac ready to be plotted
 => (IHS, ims_uac, Calling) using IHS.dat, 3
 => (SAPS, ims_uac, Calling) using SAPS.dat, 3
PX_TRT-PMM1  ready to be plotted
 => (PX_TRT-PMM1, , Messaging) using PX_TRT-PMM1.dat, 2
 => nothing to plot ()
PX_TRT-PMM2  ready to be plotted
 => (PX_TRT-PMM2, , Messaging) using PX_TRT-PMM2.dat, 2
 => nothing to plot (Failed to open PX_TRT-PMM2.dat)
set terminal png small size 1200 , 400
             ^
"RETRANSMITCallingims_uac-normaltime.png.gpl", line 4: unknown or ambiguous 
terminal type; type just 'set terminal' for a list
 
Waiting for all (12) gnuplot fork to be completed
 
set terminal png small size 1200 , 400
             ^
"IHSCallingims_uac-normaltime.png.gpl", line 4: unknown or ambiguous terminal 
type; type just 'set terminal' for a list
 
Unable to open file (SAPS-meantime.png): No such file or directory at 
../scripts/html2mht.pl line 139, <> line 361.
  
report.html
 
 
Test Report (ubuntu-vm)
Summary
 
This report shows the result of a benchmark run performed by "IMS Bench SIPp", 
an implementation of the IMS/NGN Performance Benchmark suite, ETSI TS 186.008.
 
The test was started on 15-Jul-2014 13:25, and the total time for the test 
execution was 0h 3m 17s. The Design Objective Capacity (DOC) has not been 
reached. The DOC is >= 1 scenarios per second.
 
The following systems and parameters were used for the test. The full list of 
IMS benchmark parameters can be found in Appendix.
Role Server IP Nb Users
SUT 1 ubuntu-vm 192.168.2.5  
Manager ubuntu 127.0.1.1  
TS1 ubuntu 192.168.2.11 100
 
Parameter Name Parameter Value Parameter Info
RingTime 5000 Ringing Time (ms)
HoldTime 120000 Conversation Time (ms)
RegistrationExpire 1000000 Registration Timeout (ms)
TransientTime 30 Time after the start of a step for which data is ignored (in 
seconds)
 
The following table shows the average of the key measurements for each step of 
the test. Each steps is characterized by the requested load, the effective 
load, the global IHS (total of all Inadequately handled scenarios for this step 
divided by number of Session Attempts for this step) the scenario IHS (number 
of inadequately handled scenarios for this step divided by the number of 
scenario attempts for this step), the CPU utilization and the available Memory 
on the SUT. The available Memory is expressed in MegaBytes, and the requested 
and effective loads in Scenarios Attempts Per Seconds (SAPS).
 
Note that the IHS percentages represented in this table are the number of 
failures for a step divided by the number of scenario attempts for this step, 
and so is not the average of (IHS per seconds)
  Pre-registration
Requested load 1
Effective Load 0.90
Ratio ims_reg % 100.00
SIPP CPU ubuntu 8.46
SIPP MEM ubuntu 409.23
global IHS % 0.00
 
The following chapters show details on different measurement, like delay 
between two messages, response time or number of messages per seconds.
Each measurement can be represented in one of the four following forms.
 
    Evolution in function of the time. On such graphs, the raw information is 
plotted, like number of messages per seconds, or response time of each 
scenario. This graph is useful in giving for instance a good idea on the 
distribution of response times, and it's evolution over the time.
    Evolution (mean) in function of the time. While previous graph gives a good 
indication, it may sometimes be easier to see the evolution of the mean of the 
measurement over a second in function of the time.
    Histogram. This graph shows the histogram of the measurement, so how many 
times each value of the measurement occured.
    Probability. This graph gives the probability of the measurement to be 
higher than a certain value. This graph can be used to determine percentile for 
instances.
 
For some graphs, a cubic Bezier curve is plotted as well.
 
1 Scenario Attempts Per Second
    1.1 Scenario Attempts Per Second (Mean per second)
2 SUT CPU %
3 SUT Available Memory [MB]
4 ALL SIPP CPU %
    4.1 ALL SIPP CPU % over time
5 ALL SIPP Free Memory [MB]
    5.1 ALL SIPP Free Memory [MB] over time
6 Inadequately handled scenario Percentage
    6.1 Inadequately handled scenario Percentage over time
7 Scenario retransmissions - all scenarios
    7.1 Scenario retransmissions - all scenarios over time
7 Registration
    7.1 PX_TRT-REG1: Time of the first register transaction
    7.1.1 PX_TRT-REG1: Time of the first register transaction(Registration use 
case) (Mean per second)
    7.2 PX_TRT-REG2: Time of the second register transaction
    7.2.1 PX_TRT-REG2: Time of the second register transaction(Registration use 
case) (Mean per second)
    7.3 ims_reg : Scenario retransmissions
    7.3.1 Scenario retransmissions(ims_reg scenario) over time
    7.4 ims_reg : PX_TRT-REG1: Time of the first register transaction
    7.4.1 PX_TRT-REG1: Time of the first register transaction(ims_reg scenario) 
(Mean per second)
    7.5 ims_rereg : Time of the re-register transaction
    7.6 ims_dereg : PX_TRT-REG1: Time of the first register transaction
8 Calling
    8.1 PX_TRT-SES1: Session Setup Time
    8.2 PX_TRT-SES2: Session Initiation transversal time
    8.3 PX_TRT-REL1: Delay Between BYE and 200 OK 
    8.3.1 PX_TRT-REL1: Delay Between BYE and 200 OK (Calling use case) (Mean 
per second)
    8.4 PX_TRT-SES3: INVITE and re-INVITE cost
    8.5 ims_uac : Scenario retransmissions
    8.5.1 Scenario retransmissions(ims_uac scenario) over time
    8.6 ims_uac : Inadequately handled scenario Percentage
    8.6.1 Inadequately handled scenario Percentage(ims_uac scenario) over time
9 Messaging
    9.1 PX_TRT-PMM1: Message Transmission time
    9.2 PX_TRT-PMM2: Message Transmission time (error case)
Appendix
 
1 Scenario Attempts Per Second Index
 
This graph represents the number of scenario per seconds generated by the test 
system. For each step, the generation was based on a Poisson.
     Effective Load
Step Requested Load Mean Variance Standard Deviation Minimum Maximum Percentile 
50  Percentile 90  Percentile 95  Percentile 99
Pre-reg 1 0.90 0.09 0.30 0.00 1.00 1.0 1.0 1.0 1.0
1.1 Scenario Attempts Per Second (Mean per second) Index
SAPS-meantime.png text
2 SUT CPU % Index
 
This graph represents the CPU of the system under test (SUT).
3 SUT Available Memory [MB] Index
 
This graph represents the Available memory on the system under test, in MBytes 
(SUT).
4 ALL SIPP CPU % Index
 
This graph represents the CPU of SIPP on ALL Test Machines
     SIPP CPU ubuntu
Step Requested Load Mean Standard Deviation Minimum Maximum
Pre-reg 1 8.46 2.99 4.02 14.50
4.1 ALL SIPP CPU % over time Index
ALL-SIPP-CPU-normaltime.png text
5 ALL SIPP Free Memory [MB] Index
 
This graph represents the free memory of SIPP on ALL Test Machines, in MBytes
     SIPP MEM ubuntu
Step Requested Load Mean Standard Deviation Minimum Maximum
Pre-reg 1 409.23 0.06 409.17 409.36
5.1 ALL SIPP Free Memory [MB] over time Index
ALL-SIPP-MEM-normaltime.png text
6 Inadequately handled scenario Percentage Index
 
This graph represents the percentage of inadequately handled scenarios.
     IHS per use_case %
Step Requested Load Mean Standard Deviation Minimum Maximum
Pre-reg 1 0.00 0.00 0.00 0.00
6.1 Inadequately handled scenario Percentage over time Index
IHS-normaltime.png text
7 Scenario retransmissions - all scenarios Index
 
This graph represents the number of retransmissions per seconds for all 
scenarios.
     RETRANSMIT
Step Requested Load Mean Standard Deviation Minimum Maximum Percentile 50  
Percentile 90  Percentile 95  Percentile 99
Pre-reg 1 0.00 0.00 0.00 0.00 0.0 0.0 0.0 0.0
7.1 Scenario retransmissions - all scenarios over time Index
RETRANSMIT-normaltime.png text
7 Registration Index
7.1 PX_TRT-REG1: Time of the first register transaction Index
 
This graph represents the time of the first register transaction in the 
registration use_cases i.e. the time between the REGISTER and the 401 
Unautorized for all scenarios in the Registration use_case.
     PX_TRT-REG1 (msec)
Step Requested Load Mean Standard Deviation Minimum Maximum Percentile 50  
Percentile 90  Percentile 95  Percentile 99
Pre-reg 1 55.02 28.81 24.85 106.49 37.2 106.4 106.4 106.4
7.1.1 PX_TRT-REG1: Time of the first register transaction(Registration use 
case) (Mean per second) Index
PX_TRT-REG1Registration-meantime.png text
7.2 PX_TRT-REG2: Time of the second register transaction Index
 
This graph represents the time of the second register transaction in the 
registration use_cases, i.e. the delay between the second REGISTER and the 200 
OK.
     PX_TRT-REG2 (msec)
Step Requested Load Mean Standard Deviation Minimum Maximum Percentile 50  
Percentile 90  Percentile 95  Percentile 99
Pre-reg 1 53.55 21.82 23.82 105.00 49.5 105.0 105.0 105.0
7.2.1 PX_TRT-REG2: Time of the second registe
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to