I keep seeing the definition of nodal processing delay as "The time it takes to process a packet in a network node (router, switch, hub, etc.), which is dependent on the speed of the device and congestion in the network. Contrast with propagation delay".

My question is, a node can be anything on the network (including recipient computer), so does nodal delay include things such as the amount of time the recipient takes to read the packet? What if the traffic is going through a proxy or VPN, would the intermediate computer be included in the processing delay too?

  • Did any answer help you? If so, you should accept the answer so that the question doesn't keep popping up forever, looking for an answer. Alternatively, you can provide your own answer and accept it. – Ron Maupin Aug 7 '17 at 16:23

(Nodal) Processing Delay

The (nodal) processing delay is every device along the communication path that actually processes/examines the packets; these include routers, switches, and statistical multiplexers. The receiver doesn’t count towards this delay because the receiver is the receiver and has received the packet at that point, it doesn’t matter what will be done on its side with the signal.[1][2]

Regarding proxies and VPNs: yes, every device that does anything with the packets counts towards the delays. Especially NATs (rewriting) or devices that perform deep packet inspection add a lot of processing time.

nodal processing = node processing

nodal processing ≠ nodal delay

(Total) Nodal Delay

The (total) nodal delay on the other hand is the sum of all latency delays. There are exactly four delays:

  • (Nodal) Processing Delay amount of time used to process the packet headers, check for bit errors and determine the destination host.
  • Queuing Delay amount of time a packet is waiting in the queue (buffer) before it can be pushed on the link.
  • Transmission Delay amount of time necessary to push all the bits on the link.
  • Propagation Delay amount of time it takes the signal’s header to travel from the sender to the receiver.

dnodal = dproc + dqueue + dtrans + dprop

According to Table 1 in this paper typical timings for each delays are:

  • dproc = 10–1,000 µs
  • dqueue = 0…∞
  • dtrans = 10 µs[3]
  • dprop = 1,000 µs

The queue delay may reach infinity and the whole network suffers from congestion collapse; which actually happened during the 1980s and was the reason why Congestion Avoidance and Control was invented.

As a packet travels from one node (host or router) to the subsequent node (host or router) along this path, the packet suffers from several types of delays at each node along the path. The most important of these delays are the nodal processing delay, queuing delay, transmission delay, and propagation delay; together, these delays accumulate to give a total nodal delay.

— (Kurose and Ross 2013, 35–36)

This is only a very terse primer on the subject, I encourage you to read on.



[1] Of course it matters, but it doesn’t matter for the delay calculations because we are only interested in the delay incurred by the underlying network and not the delays within sender and receiver.

[2] I’ve seen that the receiver is sometimes counted as well. I don’t know if this is correct or not, a good reference is needed here.

[3] This number is much higher in real world and highly depends on the distance to cover, also the last mile problem is very important here.

| improve this answer | |
  • Nice explanation about (end to end) network delay, but the question is about the definition of the nodal delay. I am not sure about its definition, but the first Wikipedia article in your references disagrees with you, it mentions nodal delay as a synonym for the processing delay. – Gerben Oct 20 '14 at 16:26
  • Please read my answer again and then revisit the Wikipedia article. It says nodal processing and not nodal delay, those are two different things. I think I made that clear with my answer by stating (nodal) processing delay. The joke is, processing can only happen at a node so it's a nodal processing delay but all delays together are the nodal delay (note that there is no processing). Hope this makes it even clearer. Added some headings to the answer. – Fleshgrinder Oct 20 '14 at 17:44
  • A correction to the answer of Fleshgrinder; Footnote [3] says: "This number is much higher in real world and highly depends on the distance to cover,..." "this number" in his answer is dtrans (i.e. transmission delay.) Here the correction: transmission delay has NOTHING to do with distance of the link!!! (see the first reference mentioned by Fleshgrinder: Kurose, James F.; Ross, Keith W. (2013): “Computer Networking. A Top-Down Approach”. 6th ed. Pearson Education Transmission delay is L/R where L is number of bits and R is rate (in bit/sec) propagation delay depends on the distanc – user20181 Nov 1 '15 at 7:50

Nodal delay would be delay from a node in the network path, this is to separate it from delay caused by circuit length (distance/speed of light in fiber, etc.) or client/server delay.

If the packet is passing through a VPN, the VPN device is a 'network node' to the packet and would be counted.

| improve this answer | |
  • A lot of nodal delay can come from queuing delays on the ingress and egress interfaces – Mike Pennington Oct 18 '14 at 19:07
  • I'm not clear on what you're saying. So you're saying propagation delay doesn't count for nodal delay, because that directly contradicts what @Flesgrinder says. – Celeritas Oct 20 '14 at 3:33
  • I could be completely wrong... I wouldn't consider the 'propagation delay' to be counted as part of the general 'nodal delay' sum, but there are other links (d.umn.edu/~gshute/net/delays-losses.xhtml) that indicate @Fleshgrinder is correct. I'm not a network researcher, so I could be interpreting a technical term with a well-defined meaning incorrectly. – cpt_fink Oct 20 '14 at 4:07
  • @cpt_fink if you see fit upvote the question so that more attention is given to it – Celeritas Oct 20 '14 at 4:25
  • Please check my extended answer on the confusion of nodal processing delay and nodal delay. – Fleshgrinder Oct 20 '14 at 7:41

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.