golang/go

net/http/httptest: optional faster test server

Closed

#14,200 opened on Feb 2, 2016

View on GitHubContributor guide
 (19 comments) (9 reactions) (0 assignees)Go (19,008 forks)batch import
FeatureRequestNeedsFixPerformancehelp wanted

Repository metrics

Stars
 (133,883 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Look into making httptest.Server have a way to use in-memory networking (i.e. net.Pipe) instead of localhost TCP. Might be faster/cheaper and not hit ephemeral port issues under load?

Contributor guide

Research direction
This issue proposes an in memory networking option for httptest.Server. Start by reviewing the current implementation of httptest.Server in the Go source code (net/http/httptest/server.go). Explore how net.Pipe works and consider the design implications for the test server. Examine comments in the issue thread (comments 1-19) for prior ideas and concerns. There are no linked PRs, so the implementation is open. Focus on performance benchmarks and trade offs between TCP and in memory networking.
Tech stack
go
Domain
testingperformance
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
Go programmingnet/http/httptest packagenet.PipeGo testing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10