Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • N node-http-proxy
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 482
    • Issues 482
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 102
    • Merge requests 102
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • http ... PARTY!
  • node-http-proxy
  • Issues
  • #873
Closed
Open
Issue created Aug 29, 2015 by Administrator@rootContributor

benchmark failed when using more threads

Created by: tyrchen

When I use 100 connections with 8 threads:

➜ node-http-proxy git:(master) ✗ wrk -c 100 -d1m -t 8 http://127.0.0.1:8000

The proxy server will quit after a while:

➜ node-http-proxy git:(master) ✗ node benchmark/scripts/proxy.js /Users/tchen/projects/startup/study/node-http-proxy/lib/http-proxy/index.js:119 throw err; ^ Error: read ECONNRESET at exports._errnoException (util.js:746:11) at TCP.onread (net.js:559:26)

Probably the proxy.js shall silently drop the errors to let the benchmark finish.

Assignee
Assign to
Time tracking