Reference in networking area is Standard and RFC.
This is the RFC for some performance metrices:
RFC 2679 : One-way delay metrices
RFC 2680 : One-Way packet Loss Metrices
RFC 2678 : IPPM Metrtices for Measuring Connectivity
RFC 2330 : Framework for IPPM
RFC 2681 : Round Trip Delay Metric for IPPM
RFC 3393 : Packet Delay Variation Metric for IP Performance Metrics
Thursday, May 21, 2009
Performance Parameter
When we conduct a simulation study , what we really want is the network performance of certain network.
There are four main basic parameter for network analysis
1) Delay
Measurement of how long the packet will travel from source to destinations
2) Jitter
Measurement of variations of delay
3) Packet Loss
Measurement how many packet dropped
4) Throughput
How many packets successfully sent to the
The network performance parameter can be measured at:
1) from end to end
2) between two nodes
The network performance can also be differentiated between traffic type or for all traffic.
There are four main basic parameter for network analysis
1) Delay
Measurement of how long the packet will travel from source to destinations
2) Jitter
Measurement of variations of delay
3) Packet Loss
Measurement how many packet dropped
4) Throughput
How many packets successfully sent to the
The network performance parameter can be measured at:
1) from end to end
2) between two nodes
The network performance can also be differentiated between traffic type or for all traffic.
Tuesday, May 19, 2009
NS-3 to replace NS-2?
Have you tried out NS-3?
This is what I got from http://www.nsnam.org/ official website of NS-3.
"ns-3 is intended as an eventual replacement for the popular ns-2 simulator. The project acronym “nsnam” derives historically from the concatenation of ns (network simulator) and nam (network animator). "
From user point of view, I noticed the main difference between NS-3 and NS-2 is the changes in language. Now NS-3 is using C++ and phyton, compared to NS-2 which used C and oTCL.
This means that for those who learn TCL for the sake of using NS-2 now need to learn other language for using NS-3.
Start from zero!
This is what I got from http://www.nsnam.org/ official website of NS-3.
"ns-3 is intended as an eventual replacement for the popular ns-2 simulator. The project acronym “nsnam” derives historically from the concatenation of ns (network simulator) and nam (network animator). "
From user point of view, I noticed the main difference between NS-3 and NS-2 is the changes in language. Now NS-3 is using C++ and phyton, compared to NS-2 which used C and oTCL.
This means that for those who learn TCL for the sake of using NS-2 now need to learn other language for using NS-3.
Start from zero!
Monday, May 18, 2009
NAM Editor , have you ever try it out?
Another tools to support NS2 is NAM EDITOR, do you NAM Editor? I have experience trying it, it is a good tool where you can draw network graphically then convert it to NS2 simulation script. However, I have prolme when dragging the network component.
It suddenly give segmentation fault error. What is the reason? I don't know but from my reading it is because something wrong with the C coding.. but the NAM Editor is based on TCL\TK. Hrm.. A question mark there!
It suddenly give segmentation fault error. What is the reason? I don't know but from my reading it is because something wrong with the C coding.. but the NAM Editor is based on TCL\TK. Hrm.. A question mark there!
Sunday, May 17, 2009
Tracegraph
Since there are no available trace analysis tool developed in NS2, people are building their own program. A good software was designed called tracegraph, although tracegraph is good for analysis purpose, the main problem with tracegraph is it is very slow to load a trace file.
The fact that it is created using MATLAB make it clear, since, MATLAB is not suitable to read a complex data although MATLAB is good for complex calculation. Why is it slow? It is because, the trace file need to be converted into Tracegraph format, the conversion part take 90% of the whole process.
For those using Tracegraph, make sure your computer is fast enough. However, the graphing part/ processing part is quite fast.
The fact that it is created using MATLAB make it clear, since, MATLAB is not suitable to read a complex data although MATLAB is good for complex calculation. Why is it slow? It is because, the trace file need to be converted into Tracegraph format, the conversion part take 90% of the whole process.
For those using Tracegraph, make sure your computer is fast enough. However, the graphing part/ processing part is quite fast.
Subscribe to:
Posts (Atom)