Project

General

Profile

Actions

Feature #7061

closed

local TCP connections should be expediently purged from TIME_WAIT

Added by Robert Mustacchi over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Category:
networking
Start date:
2016-06-06
Due date:
% Done:

100%

Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:
External Bug:

Description

An individual was running an HTTP-based benchmark locally in a native smartos zone. Due to the high transaction rate, TCP connections were piling up in TIME_WAIT state. Even with the best-case localhost behavior being fired every TCP_TIME_WAIT_DELAY (5s), we're left with a maximum connection rate of ~6500/s.

Since these connections are all local to the host (over localhost for this specific example), it should be safe to immediately purge the connection instead of letting it languish in TIME_WAIT.

Actions

Also available in: Atom PDF