PerformanceNotesArchive1

Benchmark scans

nmap-* are with Nmap trunk. nmap-perf-r* are revisions from the nmap-perf branch.

Guide to notation

0:02:08
10–34355
means that a scan took 0:02:08, had 10 hosts up, 34 open ports, and 355 closed ports.

Plain scans

nmap -n -d -PN -p 1-65535 scanme.nmap.org -oA perf-scanme
nmap -n -d -PN -p 1-65535 -iL perf-lan-hosts -oA perf-lan
nmap -n -d -sP -PS21,23,80,3389 -PE -iL perf-down-hosts -oA perf-down-ping
nmap -n -d -sP -PS21,23,80,3389 -PE -iL perf-up-hosts -oA perf-up-ping
nmap -n -d -F -iL perf-random-hosts -oA perf-random-F
nmap -n -d -PN -F -iL perf-up-hosts -oA perf-up-F

The first round of testing was done with the options as shown above. perf-random-hosts is 9991 random IP addresses. perf-down-hosts is 500 (initially) down addresses. perf-up-hosts is 656 (initially) up addresses. perf-lan-hosts contains 192.168.0.1 and 192.168.0.190, two live hosts on my LAN.

 scanmelandown-pingup-pingrandom-Fup-F
nmap-1 0:08:54
2–7
0:09:51
1–0
0:02:14
614–0
2:48:56
463–910
2:30:34
656–1913
nmap-3*0:11:15
1–3
0:08:51
2–7
0:11:33
4–0
0:02:25
549–0
2:09:35
464–968
3:08:14
656–1858
nmap-4**0:16:34
1–3
0:13:14
2–7
0:05:22
7–0
0:03:45
521–0
2:13:45
449–1058
2:51:21
656–1890
nmap-perf-r11208 0:08:46
2–7
0:07:31
5–0
0:03:43
541–0
3:00:41
477–1045
3:54:18
656–1882
nmap-perf-r112090:16:01
1–3
0:08:52
2–7
0:07:08
6–0
0:05:25
537–0
2:29:58
429–852
3:53:31
656–1858
nmap-perf-r11218*0:30:32
1–3
0:08:53
2–7
0:01:10
9–0
0:03:02
529–0
***2:25:36
656–1884
* nmap-2 was accidentally overwritten with nmap-3.
** Run with -d4, may be slower.
*** Ran out of disk space.

No scan delay

The second round of testing was with Nmap trunk and --max-scan-delay 0. I was trying to see if scan delay could be isolated as the cause of scan time variability.

The scans are mostly the same as in the first round, except for the maximum scan delay and the host lists. This time I used a list of 30 /26 netblocks (1920 IP addresses total).

 scanmelandown-pingup-pingrandom-Fup-F
nmap-10:16:19
1–3
0:06:26
3–9
0:00:47
4–0
0:00:40
187–0
1:56:13
700–291
0:18:48
200–6171
nmap-20:15:18
1–3
0:06:36
3–9
0:00:46
38–0
0:00:24
174–0
2:33:18
735–396
0:22:18
200–6168
nmap-30:10:00
1–3
0:06:23
3–9
0:01:08
27–0
0:00:38
176–0
2:29:44
740–333
0:20:05
200–6162

Remove dynamic addresses, no scan delay

The results from round two still vary too much. I went through the list of hosts and culled any blocks that seemed to be dynamic address ranges. That left 11 /26 netblocks (704 addresses total). I then re-ran the tests with this list in the file perf-random-hosts-2. perf-up-hosts-2 and perf-down-hosts-2 are groups of 200 up and down hosts from the list of 704.

nmap -n -d --max-scan-delay 0 \
  -PN -p 1-65535 scanme.nmap.org -oA perf-scanme
nmap -n -d --max-scan-delay 0 \
  -PN -p 1-65535 192.168.0.0/24 -oA perf-lan
nmap -n -d --max-scan-delay 0 \
  -sP -PS21,23,80,3389 -PE -iL perf-down-hosts-2 -oA perf-down-ping
nmap -n -d --max-scan-delay 0 \
  -sP -PS21,23,80,3389 -PE -iL perf-up-hosts-2 -oA perf-up-ping
nmap -n -d --max-scan-delay 0 \
  -F -iL perf-random-hosts-2 -oA perf-random-F
nmap -n -d --max-scan-delay 0 \
  -PN -F -iL perf-up-hosts-2 -oA perf-up-F
 scanmelandown-pingup-pingrandom-Fup-F
nmap-10:09:58
1–3
0:06:31
3–9
0:03:21
1–0
0:00:03
198–0
0:11:33
94–105
0:11:21
200–6307
nmap-20:10:01
1–3
0:06:33
3–9
0:00:34
2–0
0:00:11
197–0
0:09:30
94–105
0:10:31
200–6306
nmap-30:09:16
1–3
0:06:39
3–9
0:02:15
3–0
0:00:08
196–0
0:09:42
93–105
0:10:08
200–6309

Remove dynamic addresses, no retries

The same as round three, without --max-scan-delay and with --max-retries 0.

 scanmelandown-pingup-pingrandom-Fup-F
nmap-10:06:07
1–3
0:01:35
3–8
0:00:06
2–0
0:00:01
136–0
0:01:13
1–0
0:03:06
200–4984
nmap-20:05:59
1–3
0:01:24
3–8
0:00:09
3–0
0:00:02
132–0
0:01:13
1–0
0:02:58
200–4844
nmap-30:06:27
1–3
0:01:31
3–8
0:00:13
1–0
0:00:02
146–0
0:01:13
1–0
0:03:00
200–4616

Remove dynamic addresses, no scan delay, no retries

The same as round three, with both --max-scan-delay 0 and --max-retries 0.

 scanmelandown-pingup-pingrandom-Fup-F
nmap-10:05:43
1–3
0:01:30
3–8
0:00:10
1–0
0:00:01
158–0
0:01:13
1–0
0:03:10
200–5050
nmap-20:06:33
1–3
0:01:25
3–7
0:00:12
2–0
0:00:01
173–0
0:01:13
1–0
0:03:16
200–4875
nmap-30:06:26
1–3
0:01:25
3–8
0:00:06
1–0
0:00:03
136–0
0:01:13
1–0
0:03:02
200–4916

Baseline scans, no scan delay, one retry

Baseline scans with --max-scan-delay 0 --max-retries 1.

nmap -n -d --max-scan-delay 0 --max-retries 1 \
     -PN -p 1-65535 scanme.nmap.org -oA perf-scanme
nmap -n -d --max-scan-delay 0 --max-retries 1 \
     -PN -p 1-65535 192.168.0.0/24 -oA perf-lan
nmap -n -d --max-scan-delay 0 --max-retries 1 \
     -sP -PS21,23,80,3389 -PE -iL perf-down-hosts-2 -oA perf-down-ping
nmap -n -d --max-scan-delay 0 --max-retries 1 \
     -sP -PS21,23,80,3389 -PE -iL perf-up-hosts-2 -oA perf-up-ping
nmap -n -d --max-scan-delay 0 --max-retries 1 \
     -F -iL perf-random-hosts-2 -oA perf-random-F
nmap -n -d --max-scan-delay 0 --max-retries 1 \
     -PN -F -iL perf-up-hosts-2 -oA perf-up-F
 scanmelandown-pingup-pingrandom-Fup-F
nmap-r112380:09:53
1–3
0:04:17
3–9
0:01:20
1–0
0:00:15
196–0
0:08:37
91–109
0:09:38
200–6290
nmap-r112380:10:00
1–3
0:04:17
3–9
0:03:22
1–0
0:00:03
196–0
0:09:56
89–110
0:09:25
200–6291
nmap-112530:12:04
1–3
0:03:54
3–9
0:03:43
1–0
0:00:15
195–0
0:08:39
91–104
0:08:16
200–6265

Summary of changes:

A picture of the r11253 change:
r11252: 
r11253: 
Probably the main noticeable difference is that cwnd doesn't instantly jump up to ssthresh at the beginning.

nmap-perf r11348, same as baseline

 scanmelandown-pingup-pingrandom-Fup-F
scan-delay-perf-r113480:12:34
1–3
0:03:55
3–9
0:00:27
2–0
0:00:13
195–0
0:08:23
94–109
0:08:06
200–6284

Scan rate as affected by scan delay

Scans on the left are nmap -n -PN -d3 -F -sU 192.168.0.1. Scans on the right are nmap -n -PN -d3 -p1-30000 -sS 192.168.0.190.

The gray line is the enforced maximum scan rate. The black line is the actual scan rate, as measured by a RateMeter.

r11260 – same as nmap trunk

open|filtered 5 closed 95open 3 closed 29997

r11273 – scan delay replaced with max rate

open|filtered 6 closed 94open 3 closed 29997

r11279 – max rate half of current rate on first drop (TCP only)

open|filtered 6 closed 94open 3 closed 29997

r11283 – allow max rate to increase up to most recent drop

open|filtered 5 closed 95open 3 closed 29997

r11284 – linear growth of max rate with decay in growth rate

open|filtered 5 closed 95open 3 closed 29997

r11322 – max rate based on measured receive rate

open|filtered 5 closed 95open 3 closed 29997

r11323 – no scan rate drops with max_successful_tryno increase

open|filtered 5 closed 95open 3 closed 29997

r11326 – allow recovery of maximum scan rate

open|filtered 5 closed 95open 3 closed 29997

r11342 – scale measured receive rate by receipt ratio

open|filtered 8 closed 92open 3 closed 29044 filtered 953

r11347 – no enforced delay with increase in tryno

open|filtered 93 closed 7open 3 closed 29997

r11348 – max rate recovery rate proportional to max rate

open|filtered 93 closed 7open 3 closed 29997

r11351 – contract congestion window at new tryno

open|filtered 5 closed 95open 3 closed 29997

r11368 – update receive rate meter when measuring

open|filtered 5 closed 95open 3 closed 29997

r11373 – normalize receive rates in the first second

open|filtered 5 closed 95open 3 closed 29997

r11383 – divide response rate by responsiveness ratio (like r11342 but better)

open|filtered 5 closed 95open 3 closed 29997
 scanmelandown-pingup-pingrandom-Fup-F
nmap-10:13:11
1–3
0:03:57
3–9
0:02:24
4–0
0:00:17
194–0
0:09:15
97–104
0:08:12
200–6255
nmap-20:12:58
1–3
0:03:53
3–9
0:02:45
4–0
0:00:20
194–0
0:08:48
98–103
0:07:55
200–6289
nmap-30:12:53
1–3
0:03:54
3–9
0:00:29
4–0
0:00:29
194–0
0:09:10
98–112
0:08:11
200–6265
nmap-perf-r11383-10:12:33
1–3
0:05:51
3–9
0:00:57
5–0
0:00:21
194–0
0:09:06
99–112
0:09:40
200–6283
nmap-perf-r11383-20:13:03
1–3
0:07:42
3–9
0:05:18
2–0
0:00:06
193–0
0:09:36
95–105
0:10:23
200–6288
nmap-perf-r11383-30:12:11
1–3
0:05:09
3–9
0:01:21
2–0
0:00:32
194–0
0:10:10
97–107
0:09:19
200–6270

r11384 – fix incorrect resetting of the responsiveness ratio

open|filtered 5 closed 95open 3 closed 29997
 scanmelandown-pingup-pingrandom-Fup-F
nmap-perf-r11384-10:12:30
1–3
0:07:50
3–9
0:04:45
0–0
0:00:04
194–0
 0:10:13
200–6292

r11409 – use ratio of sending to receiving rate

open|filtered 5 closed 95open 3 closed 29997

r11410 – use current receive rate, not overall

open 1 open|filtered 4 closed 95open 3 closed 29997

r11458 – use a combination of rate ratios and drop ratios

open|filtered 6 closed 94open 3 closed 29997

r11461 – count all probes for reponsiveness; revert responsiveness on drop

open 1 open|filtered 5 closed 94open 3 closed 29997

r11465 – cache responsiveness for pings too

open 1 open|filtered 4 closed 95open 3 closed 29997

r11472 – merge from main

open 1 open|filtered 4 closed 95open 3 closed 29997

r11479 – undo r11461

open 1 open|filtered 4 closed 95open 3 closed 29997

r11480 – reduce max rate more severely

open 1 open|filtered 4 closed 95open 3 closed 29997

What's the right speed to scan anyway?

Because the overall times taken are still fairly variable, I was curious about what really is the optimum fixed rate at which to scan these hosts. I made a script rate-test.sh that ran multiple scans at fixed rates near the hosts' supposed rate limits. These graphs show the results of several trials using nmap-perf r11480.

On the left is a UDP scan of a Linux host with a nominative rate limit of 1 ICMP reply per second. It seems the optimal scanning rate is actually 1.1 send per second, but going even a little faster than that incurs a penalty. It may be because there are 5 open|filtered ports that we can go a little faster than we think. Every scan in these tests was 100% accurate (5 open|filtered, 95 closed).

On the right is a TCP scan of 30,000 ports on Mac OS X, with a supposed RST rate limit of 250 per second. The rate limiter had been settling in at around 150 packets per second. You can see that around 230 sends per second scan times become quite variable. Worse, much about 150 sends per second the scan is not always 100% accurate. There should be 3 open ports and 29997 closed, but some ports were found filtered at 160, 170, 190, 195, 200, 205, 215, 220, 225, 230, 235, 240, 250, 255, 260, 265, 270, 275, 280, 285, 290, 295, and 300 sends per second.

I repeated the experiment with nmap trunk (with fewer trials, using some revision near r11480) just to make sure it was the same as nmap-perf (it should be when using a fixed rate).

The results are the same. So with this in mind I'll leave no more than 5% headroom between the maximum sending rate and the measured receive rate.

r11484 – aim for 5% excess

open 1 open|filtered 4 closed 95open 3 closed 29997

r11488 – delay to allow rate meter to settle

open 1 open|filtered 4 closed 95open 3 closed 29997

r11496 – directly settle the rate meter

open 1 open|filtered 7 closed 92open 3 closed 29997

r11507 – undo r11480

open 1 open|filtered 4 closed 95open 3 closed 29997

r11508 – go to 105% receive rate on rate drop

open 1 open|filtered 4 closed 95open 3 closed 29997

r11511 – only one drop per call to ultrascan_adjust_max_rate

open 1 open|filtered 4 closed 95open 3 closed 29997

r11520 – go back to one-second delay on new tryno

open|filtered 5 closed 95open 3 closed 29997

r11522 – restore congestion window contraction

open 1 open|filtered 4 closed 95open 3 closed 29997

r11528 – exponential smoothing of drop ratio, α = 0.10

open 1 open|filtered 4 closed 95open 3 closed 29997

r11529 – α = 0.90

open 1 open|filtered 4 closed 95open 3 closed 29997

r11544 – pause rate meters while waiting on a tryno increase

open 1 open|filtered 4 closed 95open 3 closed 29997

r11546 – remove 10-probe minimum between rate changes (effective 4-probe minimum now with α = 0.90)

open 1 open|filtered 4 closed 95open 3 closed 29997

Benchmark results of nmap r11560 vs. nmap-perf r11554

nmap -n -d --log-errors --max-retries 1 \
     -p 1-65535 scanme.nmap.org -oA perf-scanme
nmap -n -d --log-errors --max-retries 1 \
     -sP -PS21,23,80,3389 -PE -iL perf-down-hosts-2 -oA perf-down-ping
nmap -n -d --log-errors --max-retries 1 \
     -sP -PS21,23,80,3389 -PE -iL perf-up-hosts-2 -oA perf-up-ping
nmap -n -d --log-errors --max-retries 1 \
     -F -iL perf-random-hosts-2 -oA perf-random-F
nmap -n -d --log-errors --max-retries 1 \
     -PN -F -iL perf-up-hosts-2 -oA perf-up-F
 scanmedown-pingup-pingrandom-Fup-F
david/nmap-10:11:08
1–33
0:06:52
4–00
0:00:02
193–00
0:10:55
101–1093200
0:11:52
200–62614954
david/nmap-20:11:55
1–33
0:00:55
3–00
0:00:29
193–00
0:11:30
100–1023015
0:10:56
200–62624949
david/nmap-30:12:43
1–33
0:02:18
4–00
0:00:32
193–00
0:11:08
102–1043017
0:09:17
200–62774954
david/nmap-perf-10:12:43
1–33
0:03:15
4–00
0:00:10
193–00
*0:08:49
200–62734948
david/nmap-perf-20:12:34
1–33
0:02:47
4–00
0:00:09
193–00
0:11:45
96–1022967
0:09:30
200–62804936
david/nmap-perf-30:13:10
1–33
0:02:53
3–00
0:00:15
193–00
0:11:13
101–1043021
0:10:13
200–62684952
flog/nmap-10:09:01
1–33
0:01:11
3–00
0:00:14
193–00
0:04:42
177–1529477
0:06:05
200–62825156
flog/nmap-20:08:37
1–33
0:00:28
4–00
0:00:08
193–00
0:04:35
181–1619710
0:05:54
200–62775173
flog/nmap-30:09:05
1–33
0:00:45
3–00
0:00:19
193–00
0:06:06
178–1459524
0:08:28
200–62705164
flog/nmap-perf-10:09:21
1–33
0:01:52
5–00
0:00:08
192–00
0:06:21
180–1629718
0:06:25
200–62715151
flog/nmap-perf-20:08:48
1–33
0:03:32
4–00
0:00:06
193–00
0:05:19
178–1609463
*
flog/nmap-perf-30:08:15
1–33
0:01:27
4–00
0:00:25
193–00
0:08:29
176–1509509
0:06:13
200–62705175
goomba/nmap-10:06:31
1–33
0:01:16
5–00
0:00:04
193–00
0:14:15
182–16828170
0:22:48
200–1841515120
goomba/nmap-20:06:20
1–33
0:02:20
4–00
0:00:03
193–00
0:14:03
182–16828132
0:16:53
200–1841515120
goomba/nmap-30:06:05
1–33
0:06:17
3–00
0:00:04
193–00
0:13:35
180–16728132
0:17:33
200–1841515121
goomba/nmap-perf-10:06:57
1–33
0:08:59
4–00
0:00:06
193–00
0:17:04
182–16828123
0:14:08
200–1841515121
goomba/nmap-perf-20:07:42
1–33
0:07:49
3–00
0:00:06
193–00
0:18:04
181–16828132
0:28:03
200–1841515121
goomba/nmap-perf-30:06:31
1–33
0:02:59
4–00
0:00:12
193–00
0:16:06
181–16728133
0:17:23
200–1841515120
syn/nmap-10:00:01
0–00
0:00:40
3–00
0:00:02
193–00
0:03:30
181–1599549
0:05:56
200–63065211
syn/nmap-20:00:01
0–00
0:00:23
6–00
0:00:03
192–00
0:04:01
184–1659791
0:06:15
200–63055211
syn/nmap-30:00:01
0–00
0:00:17
5–00
0:00:03
193–00
0:03:48
183–1589791
0:03:55
200–63065211
syn/nmap-perf-10:00:02
0–00
0:02:34
3–00
0:00:10
193–00
0:08:05
181–1599601
0:04:59
200–63055211
syn/nmap-perf-20:00:01
0–00
0:02:49
5–00
0:00:06
193–00
0:06:12
184–1659789
0:05:13
200–63065210
syn/nmap-perf-30:00:01
0–00
0:00:29
4–00
0:00:04
193–00
*0:06:04
200–63065211

* These crashed early on in the first host group.

x = read.table('stats.txt')
png(filename="out.png",width=640,height=720)
par(mai=c(0.5, 1.5, 0.0, 0.0), lwd=0.5, cex=0.6)
boxplot(x[1:(length(x) / 2) * 2 - 1], at=c(1:(length(x) / 2) - 0.15), \\
boxwex=0.25, horizontal=TRUE, las=1, col="lightblue")
boxplot(x[1:(length(x) / 2) * 2], at=c(1:(length(x) / 2) + 0.15), \\
boxwex=0.25, horizontal=TRUE, las=1, col="lightgreen", add=TRUE)
dev.off()

Blue is nmap, green is nmap-perf. Boxes are arranged in nmap/nmap-perf pairs.

Benchmark results of nmap r11569 vs. nmap-perf r11570

nmap -n -d -r --log-errors --max-retries 1 \
     -p 1-65535 scanme.nmap.org -oA perf-scanme
nmap -n -d -r --log-errors --max-retries 1 \
     -sP -PS21,23,80,3389 -PE -iL perf-down-hosts-2 -oA perf-down-ping
nmap -n -d -r --log-errors --max-retries 1 \
     -sP -PS21,23,80,3389 -PE -iL perf-up-hosts-2 -oA perf-up-ping
nmap -n -d -r --log-errors --max-retries 1 \
     -F -iL perf-random-hosts-2 -oA perf-random-F
nmap -n -d -r --log-errors --max-retries 1 \
     -PN -F -iL perf-up-hosts-2 -oA perf-up-F
 scanmedown-pingup-pingrandom-Fup-F
david/nmap-40:12:25
1–33
0:01:41
4–00
0:00:25
190–00
0:10:54
98–972929
0:09:13
200–62634857
david/nmap-50:12:37
1–33
0:02:51
3–00
0:00:20
189–00
0:10:26
96–932927
0:08:14
200–62704841
david/nmap-60:11:58
1–33
0:01:57
4–00
0:00:28
190–00
0:09:37
97–953024
0:08:18
200–62714867
david/nmap-70:11:59
1–33
0:00:31
6–00
0:00:32
190–00
0:09:28
99–963032
0:08:06
200–62624861
david/nmap-80:12:47
1–23
0:01:32
4–00
0:00:20
190–00
0:10:01
96–932924
0:08:12
200–62504849
david/nmap-perf-40:12:13
1–33
0:01:14
4–00
0:00:22
190–00
0:10:34
95–932932
0:09:23
200–62604877
david/nmap-perf-50:12:01
1–33
0:07:07
3–00
0:00:05
190–00
0:10:18
95–922937
0:10:35
200–62504881
david/nmap-perf-60:12:54
1–32
0:01:01
4–00
0:00:28
190–00
0:14:36
97–1013007
0:09:17
200–62254861
david/nmap-perf-70:12:19
1–33
0:02:45
3–00
0:00:10
190–00
0:10:35
95–952930
0:09:36
200–62514876
david/nmap-perf-80:12:18
1–33
0:00:41
4–00
0:00:12
189–00
0:12:29
98–933032
0:08:43
200–62524877
flog/nmap-40:07:47
1–33
0:00:37
3–00
0:00:18
190–00
0:04:00
174–1449388
0:04:55
200–62705088
flog/nmap-50:07:46
1–33
0:00:20
3–00
0:00:39
190–00
0:03:59
174–1519441
0:05:07
200–62795085
flog/nmap-60:07:47
1–33
0:00:23
4–00
0:00:04
188–00
0:04:31
178–1489534
0:04:57
200–62615091
flog/nmap-70:07:37
1–23
0:00:48
5–00
0:00:24
190–00
0:04:19
179–1559531
0:04:50
200–62705087
flog/nmap-80:07:33
1–33
0:00:57
5–00
0:00:07
188–00
0:04:34
180–1659534
0:05:02
200–62725095
flog/nmap-perf-40:07:47
1–23
0:00:25
3–00
0:00:10
190–00
0:05:09
174–1509441
0:05:10
200–62745089
flog/nmap-perf-50:07:40
1–33
0:00:58
3–00
0:00:23
190–00
0:04:56
174–1429437
0:06:02
200–62655089
flog/nmap-perf-60:07:33
1–33
0:01:11
4–00
0:00:11
190–00
0:08:33
176–1459528
0:05:04
200–62635093
flog/nmap-perf-70:07:50
1–23
0:00:26
4–00
0:00:11
190–00
0:04:52
180–1559530
0:05:11
200–62815101
flog/nmap-perf-80:07:48
1–33
0:00:22
5–00
0:00:08
190–00
0:09:52
180–1499534
0:05:27
200–62465094
goomba/nmap-40:06:32
1–33
0:01:02
4–00
0:00:03
190–00
0:08:37
179–16127859
0:07:49
200–1840914845
goomba/nmap-50:06:37
1–33
0:08:56
3–00
0:00:03
190–00
0:08:54
179–16127857
0:07:47
200–1840914943
goomba/nmap-60:06:40
1–33
0:01:00
4–00
0:00:07
190–00
0:08:46
179–16028145
0:07:24
200–1840914844
goomba/nmap-70:06:07
1–33
0:02:20
5–00
0:00:05
190–00
0:09:24
180–16228146
0:07:38
200–1840914844
goomba/nmap-80:06:07
1–33
0:00:45
4–00
0:00:05
190–00
0:07:13
179–16327858
0:07:54
200–1840914844
goomba/nmap-perf-40:06:37
1–33
0:02:00
3–00
0:00:05
190–00
0:12:11
178–16127857
0:10:18
200–1840914838
goomba/nmap-perf-50:05:37
1–33
0:04:37
3–00
0:00:05
190–00
0:11:30
179–16127857
0:08:40
200–1840914844
goomba/nmap-perf-60:06:54
1–33
0:02:47
4–00
0:00:08
190–00
0:10:34
177–15528145
0:10:38
200–1840914857
goomba/nmap-perf-70:05:56
1–33
0:02:04
5–00
0:00:06
189–00
0:28:22
182–16228145
0:56:27
200–1840914844
goomba/nmap-perf-80:06:28
1–33
0:05:00
4–00
0:00:11
190–00
0:10:59
178–16128139
0:10:44
200–1840914844
syn/nmap-40:00:00
0–00
0:00:43
3–00
0:00:02
190–00
0:02:37
178–1499518
0:03:38
200–62965125
syn/nmap-50:00:00
0–00
0:05:25
3–00
0:00:03
190–00
0:02:13
179–1549518
0:01:30
200–62965125
syn/nmap-60:00:00
0–00
0:01:18
3–00
0:00:02
190–00
0:02:19
179–1549518
0:01:37
200–62965125
syn/nmap-70:00:00
0–00
0:03:10
3–00
0:00:02
189–00
0:02:09
178–1499518
0:03:21
200–62955125
syn/nmap-80:00:00
0–00
0:02:54
4–00
0:00:03
190–00
0:02:08
179–1529615
0:01:53
200–62965125
syn/nmap-perf-40:00:02
0–00
0:01:30
3–00
0:00:07
190–00
0:06:18
179–1549518
0:04:03
200–62965125
syn/nmap-perf-50:00:01
0–00
0:00:28
3–00
0:00:05
190–00
0:04:22
179–1539518
0:02:25
200–62965125
syn/nmap-perf-60:00:01
0–00
0:06:57
3–00
0:00:04
190–00
0:03:01
179–1479518
0:03:55
200–62965125
syn/nmap-perf-70:00:01
0–00
0:02:40
3–00
0:00:05
190–00
0:04:23
179–1519615
0:03:40
200–62965125
syn/nmap-perf-80:00:01
0–00
0:00:21
4–00
0:00:05
189–00
0:04:35
178–1459615
0:02:31
200–62935124

Notice the much compressed horizontal axis compared with the previous graph. Note: I didn't notice it at first, but there are two extreme outliers not shown on the graph. They are
goomba/nmap-perf-7/random-F 1702 s
goomba/nmap-perf-7/up-F 3387 s

Benchmark results of nmap vs. nmap-perf-alt r11587

 scanmedown-pingup-pingrandom-Fup-F
david/nmap-90:12:35
1–33
0:01:17
5–00
0:00:13
191–00
0:10:32
99–1053026
0:08:33
200–62764928
david/nmap-100:12:31
1–33
0:00:43
9–00
0:00:33
191–00
0:09:18
104–1173218
0:08:53
200–62604944
david/nmap-110:13:38
1–33
0:01:05
8–00
0:00:21
192–00
0:09:36
102–1103118
0:07:56
200–62734941
david/nmap-perf-alt-90:13:02
1–33
0:00:49
7–00
0:00:36
190–00
0:08:21
103–782947
0:06:47
200–51064408
david/nmap-perf-alt-100:12:28
1–33
0:00:33
8–00
0:00:28
192–00
0:09:15
103–772797
0:07:24
200–51024408
david/nmap-perf-alt-110:12:33
1–33
0:01:24
7–00
0:00:24
192–00
0:07:43
98–782563
0:06:18
200–51034404
flog/nmap-90:08:27
1–33
0:01:00
5–00
0:00:12
191–00
0:04:25
180–1659623
0:04:48
200–62895174
flog/nmap-100:07:46
1–33
0:01:08
4–00
0:00:03
190–00
0:04:02
179–1679601
0:04:47
200–62835175
flog/nmap-110:08:01
1–33
0:00:58
7–00
0:00:08
192–00
0:04:46
184–1769609
0:05:00
200–62745181
flog/nmap-perf-alt-90:07:37
1–23
0:06:18
4–00
0:00:05
192–00
0:04:55
177–1659605
0:05:18
200–62875268
flog/nmap-perf-alt-100:07:46
1–33
0:00:53
6–00
0:00:13
190–00
0:04:42
178–1639709
0:05:21
200–62815184
flog/nmap-perf-alt-110:07:52
1–33
0:00:15
8–00
0:00:23
191–00
0:05:49
186–1749794
0:05:43
200–62715178
goomba/nmap-90:05:56
1–33
0:04:26
5–00
0:00:03
192–00
0:09:26
186–17028691
0:07:46
200–1841815122
goomba/nmap-100:06:10
1–33
0:00:37
3–00
0:00:03
192–00
0:07:45
184–17228395
0:08:42
200–1841815122
goomba/nmap-110:05:22
1–33
0:00:56
7–00
0:00:03
192–00
0:09:46
187–17428691
0:10:39
200–1841715121
goomba/nmap-perf-alt-90:06:30
1–33
0:00:45
6–00
0:00:07
192–00
0:11:51
185–17228407
0:12:15
200–1841815122
goomba/nmap-perf-alt-100:06:24
1–33
0:00:36
5–00
0:00:06
192–00
0:09:58
186–17228690
0:10:50
200–1841715122
goomba/nmap-perf-alt-110:06:16
1–33
0:00:39
9–00
0:00:07
191–00
0:13:33
188–17329025
0:09:31
200–1841715120
syn/nmap-90:00:00
0–00
0:00:28
6–00
0:00:03
192–00
0:03:33
185–1719695
0:02:25
200–63095211
syn/nmap-100:00:00
0–00
0:00:48
5–00
0:00:03
192–00
0:02:22
184–1719689
0:02:17
200–63095211
syn/nmap-110:00:00
0–00
0:00:58
4–00
0:00:02
192–00
0:02:19
184–1719667
0:01:41
200–63095211
syn/nmap-perf-alt-90:00:02
0–00
0:00:24
6–00
0:00:09
192–00
0:02:59
185–1719694
0:02:03
200–63085210
syn/nmap-perf-alt-100:00:02
0–00
0:01:55
4–00
0:00:05
192–00
0:13:02
184–1719689
0:02:26
200–63095308
syn/nmap-perf-alt-110:00:01
0–00
0:02:04
4–00
0:00:04
192–00
0:02:47
184–1689688
0:03:17
200–63095211

Benchmark results of nmap vs. nmap-perf-alt r11599

 scanmedown-pingup-pingrandom-Fup-F
david/nmap-120:11:11
1–33
0:02:32
4–00
0:00:20
193–00
0:11:51
101–1052916
0:07:43
200–62584932
david/nmap-130:11:48
1–33
0:00:41
3–00
0:00:26
191–00
0:10:50
96–1032970
0:08:27
200–62744945
david/nmap-140:12:31
1–32
0:01:15
3–00
0:00:23
192–00
0:10:02
97–1073014
0:07:58
200–62874942
david/nmap-perf-alt-120:11:57
1–33
0:00:33
5–00
0:00:10
192–00
0:08:42
101–772782
0:07:03
200–50894404
david/nmap-perf-alt-130:12:08
1–33
0:02:50
3–00
0:00:27
190–00
0:11:22
97–772784
0:06:43
200–50744403
david/nmap-perf-alt-140:12:17
1–33
0:00:34
3–00
0:00:32
192–00
0:11:58
99–772789
0:05:53
200–50654402
flog/nmap-120:08:44
1–33
0:02:13
3–00
0:00:09
193–00
0:05:23
181–1639586
0:04:27
200–62595167
flog/nmap-130:07:19
1–33
0:00:27
4–00
0:00:53
192–00
0:04:26
178–1599701
0:04:40
200–62735177
flog/nmap-140:08:07
1–33
0:00:24
4–00
0:00:03
191–00
0:05:31
180–1559800
0:04:47
200–62835178
flog/nmap-perf-alt-120:07:46
1–33
0:00:25
4–00
0:00:10
191–00
0:04:44
177–1609711
0:05:31
200–62885178
flog/nmap-perf-alt-130:08:30
1–33
0:00:23
4–00
0:00:14
192–00
0:05:09
177–1499705
0:04:57
200–62815173
flog/nmap-perf-alt-140:07:35
1–33
0:01:54
6–00
0:00:20
192–00
0:08:28
180–1519803
0:05:13
200–62875179
goomba/nmap-120:06:33
1–33
0:01:55
4–00
0:00:03
192–00
0:09:14
183–17028401
0:06:32
200–1841815121
goomba/nmap-130:06:36
1–33
0:00:32
5–00
0:00:04
192–00
0:08:56
184–17028469
0:06:26
200–1841815088
goomba/nmap-140:06:37
1–33
0:00:34
3–00
0:00:03
191–00
0:09:33
180–16928398
0:07:28
200–1841715121
goomba/nmap-perf-alt-120:06:21
1–33
0:01:40
5–00
0:00:06
193–00
0:15:07
185–17028401
0:07:57
200–1841815121
goomba/nmap-perf-alt-130:06:24
1–33
0:00:34
3–00
0:00:06
191–00
0:07:30
180–16928398
0:07:32
200–1841715121
goomba/nmap-perf-alt-140:06:25
1–33
0:00:51
4–00
0:00:06
191–00
0:08:45
181–16928399
0:08:18
200–1841715121
syn/nmap-120:00:00
0–00
0:02:29
4–00
0:00:02
190–00
0:02:45
184–1699786
0:01:25
200–63095211
syn/nmap-130:00:00
0–00
0:01:10
3–00
0:00:04
192–00
0:03:19
182–1689689
0:01:24
200–63095211
syn/nmap-140:00:00
0–00
0:00:33
3–00
0:00:02
191–00
0:02:27
181–1639782
0:01:32
200–63095211
syn/nmap-perf-alt-120:00:01
0–00
0:00:55
3–00
0:00:08
192–00
0:11:03
183–1689690
0:01:49
200–63085210
syn/nmap-perf-alt-130:00:02
0–00
0:00:39
4–00
0:00:04
190–00
0:10:44
182–1629786
0:01:54
200–63095211
syn/nmap-perf-alt-140:00:01
0–00
0:00:25
4–00
0:00:05
192–00
0:02:38
182–1659785
0:01:56
200–63095211

Benchmark results of nmap vs. nmap-perf r11641

nmap-perf is a big winner in the down-ping test. nmap-perf lost against scanme, which is unusual.

 scanmedown-pingup-pingrandom-Fup-F
david/nmap-370:12:24
1–33
0:03:47
4–00
0:00:18
194–00
0:10:37
100–1083059
0:07:44
200–62845039
david/nmap-380:12:05
1–33
0:06:30
3–00
0:00:12
192–00
0:09:23
97–1062957
0:07:59
200–62885041
david/nmap-390:09:12
1–32
0:01:08
3–00
0:00:23
194–00
0:10:34
101–1133056
0:07:54
200–62415043
david/nmap-perf-370:22:46
1–33
0:00:39
3–00
0:00:20
194–00
0:14:00
98–1072956
0:08:48
200–62695054
david/nmap-perf-380:11:56
1–33
0:00:32
3–00
0:00:17
194–00
0:09:57
100–1083054
0:08:18
200–62715046
david/nmap-perf-390:19:49
1–33
0:00:26
3–00
0:00:20
194–00
0:12:31
99–1132967
0:08:18
200–62695054
goomba/nmap-370:10:28
1–33
0:04:46
4–00
0:00:06
193–00
0:19:37
183–17128822
0:08:19
200–1841915505
goomba/nmap-380:06:44
1–33
0:03:13
3–00
0:00:04
193–00
0:10:46
182–17228538
0:06:58
200–1841715507
goomba/nmap-390:06:37
1–33
0:07:40
3–00
0:00:03
194–00
0:08:37
181–17128538
0:07:08
200–1841815396
goomba/nmap-perf-370:12:13
1–33
0:00:40
4–00
0:00:09
194–00
0:08:09
180–17228538
0:07:49
200–1841915398
goomba/nmap-perf-380:07:08
1–33
0:00:24
3–00
0:00:06
194–00
0:10:57
181–17128498
0:08:46
200–1841815448
goomba/nmap-perf-390:06:55
1–33
0:01:35
3–00
0:00:06
194–00
0:09:03
183–17128539
0:10:04
200–1841815437

r11645 – extensive changes for Internet scans; same drop detection as trunk

open 1 open|filtered 4 closed 95open 3 closed 29997

Benchmark results of nmap r11645 vs. nmap-perf r11645 vs. nmap r11204

 scanmedown-pingup-pingrandom-Fup-F
goomba/nmap-400:06:42
1–33
0:04:41
4–00
0:00:03
193–00
0:09:36
183–16828268
0:10:15
200–1841715246
goomba/nmap-410:06:36
1–33
0:05:49
3–00
0:00:03
193–00
0:11:24
182–16827982
0:10:14
200–1841715260
goomba/nmap-420:06:25
1–33
0:09:00
3–00
0:00:03
193–00
0:14:42
180–16927979
0:10:57
200–1842015153
goomba/nmap-perf-400:06:49
1–33
0:00:34
4–00
0:00:05
193–00
0:09:01
183–16828248
0:07:56
200–1841715304
goomba/nmap-perf-410:07:34
1–33
0:01:48
3–00
0:00:06
193–00
0:10:32
183–16827982
0:07:24
200–1841715140
goomba/nmap-perf-420:07:02
1–33
0:02:13
3–00
0:00:05
193–00
0:10:04
181–16927981
0:12:55
200–1842015165
goomba/nmap-r11204-400:06:30
1–33
0:03:28
5–00
0:00:02
193–00
0:15:33
181–16827996
0:10:11
200–1841715178
goomba/nmap-r11204-410:05:47
1–33
0:01:44
3–00
0:00:03
192–00
0:15:24
182–16827981
0:11:29
200–1841815129
goomba/nmap-r11204-420:06:42
1–33
0:03:20
3–00
0:00:03
191–00
0:15:25
181–17127981
0:11:55
200–1842015155

Green is nmap-perf, blue is nmap, and orange is old nmap.

nmap-perf wins up-F, random-F, and down-ping. The one slow time for nmap-perf/up-F is because of a wrong rate limit set to 1.00 on one host. It took almost 300 s longer to scan than the others.

nmap-r11204/random-F is amazingly consistent, considering that test includes a ping scan and a port scan. nmap-r11204 was the fastest in the scanme test.

Benchmark results of nmap r11650 vs. nmap-perf r11650 (experimental RTT changes)

 scanmedown-pingup-pingrandom-Fup-F
goomba/nmap-430:06:54
1–33
0:03:44
5–00
0:00:04
193–00
0:08:22
183–17027970
0:07:25
200–1842015191
goomba/nmap-440:06:43
1–33
0:04:11
4–00
0:00:03
193–00
0:12:02
181–17028267
0:07:08
200–1841915132
goomba/nmap-450:06:31
1–33
0:02:08
6–00
0:00:03
193–00
0:09:49
183–17028859
0:13:26
200–1842015141
goomba/nmap-perf-430:06:27
1–33
0:00:20
5–00
0:00:06
193–00
0:09:19
183–17028258
0:11:25
200–1841915128
goomba/nmap-perf-440:07:51
1–33
0:01:13
4–00
0:00:05
193–00
0:11:22
182–17028252
0:11:48
200–1842015159
goomba/nmap-perf-450:06:46
1–33
0:00:13
6–00
0:00:05
193–00
0:10:14
183–17028968
0:23:36
200–1841815231

Benchmark results of nmap r11651 vs. nmap-perf r11651 (removal of scan delay changes)

 scanmedown-pingup-pingrandom-Fup-F
david/nmap-430:10:20
1–33
0:01:04
6–00
0:00:41
194–00
0:10:01
101–1113106
0:08:28
200–62834946
david/nmap-440:12:08
1–33
0:01:07
6–00
0:00:16
194–00
0:09:53
103–1063029
0:08:41
200–62954964
david/nmap-450:12:03
1–33
0:01:42
6–00
0:00:19
194–00
0:09:01
100–1052922
0:08:08
200–62764938
david/nmap-perf-430:11:45
1–33
0:00:26
5–00
0:00:03
193–00
0:09:54
102–1123114
0:08:09
200–62834953
david/nmap-perf-440:11:44
1–33
0:00:13
7–00
0:00:31
194–00
0:09:05
102–1043023
0:08:32
200–62894964
david/nmap-perf-450:12:00
1–33
0:00:17
6–00
0:00:17
193–00
0:10:32
99–1052926
0:08:24
200–62704952

Benchmark results of nmap r11651 vs. nmap-perf r11651 vs. nmap r11204

 scanmedown-pingup-pingrandom-Fup-F
david/nmap-460:12:28
1–33
0:02:34
2–00
0:00:26
193–00
0:09:31
96–1052869
0:07:28
200–62734914
david/nmap-470:12:26
1–32
0:01:39
3–00
0:00:02
191–00
0:09:24
94–902776
0:08:40
200–62524868
david/nmap-480:12:46
1–33
0:00:35
4–00
0:00:17
191–00
0:11:42
96–902889
0:09:02
200–62524876
david/nmap-490:11:41
1–33
0:00:29
4–00
0:00:30
190–00
0:08:54
93–922927
0:08:32
200–62484863
david/nmap-500:12:13
1–33
0:00:18
4–00
0:00:28
191–00
0:09:03
95–932927
0:08:45
200–62574956
david/nmap-perf-460:12:06
1–33
0:02:41
2–00
0:00:12
192–00
0:08:32
90–972530
0:07:56
200–62844962
david/nmap-perf-470:12:46
1–32
0:02:16
2–00
0:00:17
192–00
0:07:43
92–922788
0:08:08
200–62634859
david/nmap-perf-480:13:23
1–33
0:00:33
4–00
0:00:25
192–00
0:10:00
94–892830
0:07:44
200–62744846
david/nmap-perf-490:13:07
1–33
0:00:23
4–00
0:00:04
187–00
0:09:20
95–932931
0:08:22
200–62594869
david/nmap-perf-500:12:31
1–23
0:00:14
2–00
0:00:24
191–00
0:08:58
96–932924
0:08:32
200–62554970
david/nmap-r11204-460:09:47
1–33
0:00:55
1–00
0:00:10
193–00
0:08:08
95–752551
0:07:08
200–50964396
david/nmap-r11204-470:20:27
1–33
0:07:00
3–00
0:00:12
191–00
0:07:32
95–722561
0:07:42
200–50854328
david/nmap-r11204-480:09:55
1–33
0:00:47
4–00
0:00:10
192–00
0:07:52
98–712709
0:06:44
200–50844346
david/nmap-r11204-490:09:46
1–33
0:01:30
4–00
0:00:16
189–00
0:07:36
95–712703
0:08:31
200–50854333
david/nmap-r11204-500:10:02
1–33
0:00:23
4–00
0:00:09
190–00
0:08:54
97–712781
0:07:29
200–50694400
flog/nmap-460:09:50
1–33
0:00:12
5–00
0:00:05
187–00
0:03:57
176–1469436
0:04:49
200–62725107
flog/nmap-470:08:05
1–33
0:00:34
4–00
0:00:13
190–00
0:04:52
172–1499482
0:05:40
200–62685092
flog/nmap-480:08:22
1–33
0:00:53
4–00
0:00:11
190–00
0:04:21
174–1449426
0:05:24
200–62705196
flog/nmap-490:08:50
1–33
0:00:26
2–00
0:00:17
191–00
0:05:33
178–1499616
0:04:54
200–62725206
flog/nmap-500:08:48
1–33
0:00:35
4–00
0:00:11
190–00
0:04:29
173–1539442
0:05:04
200–62655100
flog/nmap-perf-460:08:33
1–33
0:00:11
5–00
0:00:21
191–00
0:04:16
176–1479430
0:05:18
200–62735097
flog/nmap-perf-470:08:48
1–33
0:00:10
4–00
0:00:20
189–00
0:04:45
175–1439469
0:05:21
200–62475112
flog/nmap-perf-480:08:17
1–33
0:00:11
4–00
0:00:20
191–00
0:04:27
172–1429335
0:05:16
200–62595196
flog/nmap-perf-490:08:45
1–23
0:00:10
4–00
0:00:07
190–00
0:04:41
178–1489621
0:04:54
200–62595177
flog/nmap-perf-500:07:58
1–33
0:00:11
3–00
0:00:25
188–00
0:05:00
174–1519426
0:05:12
200–62685079
flog/nmap-r11204-460:07:04
1–33
0:00:55
5–00
0:00:11
189–00
0:04:22
176–1499437
0:08:42
200–62655108
flog/nmap-r11204-470:07:21
1–33
0:00:18
4–00
0:00:26
189–00
0:04:25
173–1489438
0:09:27
200–62375099
flog/nmap-r11204-480:07:46
1–23
0:00:21
4–00
0:00:15
191–00
0:04:34
178–1479529
0:07:48
200–62585185
flog/nmap-r11204-490:07:58
1–33
0:01:13
4–00
0:00:14
191–00
0:05:41
178–1479621
0:08:04
200–62675134
flog/nmap-r11204-500:07:59
1–33
0:00:56
3–00
0:00:03
190–00
0:04:19
172–1559447
0:07:45
200–62745096
goomba/nmap-460:06:37
1–33
0:09:07
2–00
0:00:03
193–00
0:12:59
178–16927982
0:11:54
200–1841815210
goomba/nmap-470:07:07
1–33
0:07:07
3–00
0:00:04
193–00
0:09:34
180–16928016
0:06:45
200–1840714908
goomba/nmap-480:07:39
1–33
0:04:38
3–00
0:00:03
192–00
0:10:17
175–16027435
0:06:44
200–1840914982
goomba/nmap-490:07:10
1–33
0:00:14
5–00
0:00:05
191–00
0:11:24
178–16528138
0:07:29
200–1840914922
goomba/nmap-500:07:22
1–33
0:05:19
4–00
0:00:05
188–00
0:09:04
176–15927854
0:11:44
200–1840915239
goomba/nmap-perf-460:07:36
1–33
0:02:28
2–00
0:00:03
193–00
0:09:15
177–16927982
0:06:27
200–1841815241
goomba/nmap-perf-470:10:49
1–33
0:01:00
3–00
0:00:02
193–00
0:07:37
174–15827725
0:06:03
200–1840914895
goomba/nmap-perf-480:09:38
1–33
0:00:50
3–00
0:00:03
192–00
0:10:22
177–16027612
0:06:40
200–1840914949
goomba/nmap-perf-490:07:11
1–33
0:00:14
5–00
0:00:03
190–00
0:08:20
179–16027854
0:06:56
200–1840914905
goomba/nmap-perf-500:07:18
1–33
0:00:14
4–00
0:00:04
188–00
0:11:58
177–15927865
0:07:10
200–1840915295
goomba/nmap-r11204-460:06:44
1–33
0:01:01
2–00
0:00:04
189–00
0:13:51
177–16927982
0:09:40
200–1841815155
goomba/nmap-r11204-470:06:18
1–33
0:03:40
3–00
0:00:03
193–00
0:12:06
174–15827706
0:12:11
200–1840914885
goomba/nmap-r11204-480:06:02
1–33
0:02:26
3–00
0:00:03
192–00
0:14:05
177–16327890
0:10:09
200–1840914902
goomba/nmap-r11204-490:06:33
1–33
0:00:33
5–00
0:00:03
192–00
0:12:58
177–16027845
0:14:03
200–1840914856
goomba/nmap-r11204-500:10:11
1–33
0:01:21
5–00
0:00:03
188–00
0:27:57
176–16027852
0:09:31
200–1840915163
syn/nmap-460:00:00
0–00
0:04:30
5–00
0:00:02
190–00
0:02:19
179–1479616
0:02:03
200–62965139
syn/nmap-470:00:00
0–00
0:01:17
5–00
0:00:03
189–00
0:04:02
177–1499521
0:01:52
200–62965140
syn/nmap-480:00:00
0–00
0:00:13
4–00
0:00:03
190–00
0:03:53
176–1499518
0:02:05
200–62965124
syn/nmap-490:00:00
0–00
0:00:39
4–00
0:00:02
190–00
0:02:28
176–1499518
0:02:13
200–62965124
syn/nmap-500:00:01
0–00
0:00:23
5–00
0:00:02
190–00
0:02:41
176–1499518
0:01:51
200–62965124
syn/nmap-perf-460:00:00
0–00
0:00:12
5–00
0:00:03
190–00
0:02:28
179–1479616
0:01:41
200–62965045
syn/nmap-perf-470:00:01
0–00
0:00:12
5–00
0:00:02
189–00
0:02:47
178–1509562
0:01:25
200–62954992
syn/nmap-perf-480:00:00
0–00
0:00:12
4–00
0:00:03
190–00
0:02:21
177–1489597
0:01:27
200–62964991
syn/nmap-perf-490:00:00
0–00
0:00:12
4–00
0:00:04
190–00
0:02:50
176–1499518
0:01:39
200–62955145
syn/nmap-perf-500:00:00
0–00
0:00:11
4–00
0:00:04
190–00
0:02:08
177–1539608
0:01:33
200–62955163
syn/nmap-r11204-460:00:01
0–00
0:00:23
5–00
0:00:02
190–00
0:04:42
179–1499520
0:03:25
200–62965130
syn/nmap-r11204-470:00:00
0–00
0:00:47
5–00
0:00:03
189–00
0:03:33
176–1499518
0:02:45
200–62955140
syn/nmap-r11204-480:00:00
0–00
0:00:17
4–00
0:00:02
190–00
0:03:59
176–1499518
0:04:31
200–62965124
syn/nmap-r11204-490:00:00
0–00
0:00:27
4–00
0:00:02
190–00
0:04:44
176–1499518
0:04:11
200–62965139
syn/nmap-r11204-500:00:00
0–00
0:01:38
4–00
0:00:02
190–00
0:04:20
177–1549610
0:04:34
200–62945147
ucsd/nmap-46-ucsd0:02:11
1–33
0:02:10
3–00
0:00:07
657–00
0:16:39
499–1715243269
0:38:31
921–2300242187
ucsd/nmap-47-ucsd0:02:11
1–33
0:00:48
19–00
0:00:07
630–00
0:10:48
486–1666235728
0:42:48
921–2206228554
ucsd/nmap-48-ucsd0:02:10
1–33
0:00:55
12–00
0:00:07
579–00
0:20:22
437–1569209552
0:44:22
921–2082202910
ucsd/nmap-49-ucsd0:02:10
1–33
0:00:56
8–00
0:00:12
564–00
0:11:13
416–1526200706
0:43:47
921–2065201736
ucsd/nmap-50-ucsd0:02:11
1–33
0:00:56
6–00
0:00:07
560–00
0:16:54
415–1519199539
0:46:43
921–2068201847
ucsd/nmap-perf-46-ucsd0:02:10
1–33
0:02:50
4–00
0:00:05
656–00
0:09:56
492–1709239964
0:24:33
921–2290240353
ucsd/nmap-perf-47-ucsd0:02:10
1–33
0:00:55
19–00
0:00:05
632–00
0:22:08
488–1658233020
0:28:55
921–2150218323
ucsd/nmap-perf-48-ucsd0:02:11
1–33
0:00:54
13–00
0:00:08
580–00
0:09:12
429–1549206565
0:29:14
921–2078203076
ucsd/nmap-perf-49-ucsd0:02:11
1–33
0:01:43
8–00
0:00:05
562–00
0:17:12
419–1530200628
0:29:35
921–2054201205
ucsd/nmap-perf-50-ucsd0:02:10
1–33
0:01:13
6–00
0:00:06
560–00
0:09:31
416–1524200144
0:28:19
921–2056201166
ucsd/nmap-r11204-46-ucsd0:01:43
1–33
0:06:13
7–00
0:00:04
656–00
0:11:48
496–1720241821
0:39:26
921–2280239842
ucsd/nmap-r11204-47-ucsd0:01:43
1–33
0:01:03
19–00
0:00:05
631–00
0:11:28
486–1672233392
0:44:50
921–2148215583
ucsd/nmap-r11204-48-ucsd0:01:43
1–33
0:01:02
13–00
0:00:05
580–00
0:19:40
427–1546204057
0:41:22
921–2064202051
ucsd/nmap-r11204-49-ucsd0:01:43
1–33
0:01:09
8–00
0:00:06
562–00
0:11:09
414–1519199469
0:48:32
921–2057201454
ucsd/nmap-r11204-50-ucsd0:01:43
1–33
0:01:03
6–00
0:00:05
559–00
0:10:49
417–1534201153
0:51:08
921–2058201765

Same thing with a log scale (easier to compare the shorter times): Attach:nmap-perf-bench-boxplot-r11651-log.png
Another view with dots you might like better: Attach:nmap-perf-bench-stripchart-r11651.png
Dots, log scale: Attach:nmap-perf-bench-stripchart-r11651-log.png
Page last modified on January 08, 2009, at 02:09 PM