Details on python http long connection client

  • 2020-06-03 07:17:32
  • OfStack


The online machine needs to filter the access log and send it to another api

At the beginning, it was a single process, which was too inefficient. When it was changed to multi-process, abnormal errors would occasionally appear in the log (I forgot the screenshot...).

In short, the port is not enough to report an error

The reason:

Each log is sent to api once, and the short connection generates a large amount of time_wait state, occupying a large number of ports

The large amount of time_wait state kernel tuning that resulted from this high concurrency was largely useless, and was later changed to long connection to solve the problem

The key code for the short link version 1 is as follows

Because of the specific business information, only the key parts of the code are posted

import pycurl
where True:
 print send_msg.getinfo(send_msg.HTTP_CODE)

The modified version of long connection is as follows:

Using requests library

import requests
headers = {'Content-Type': 'application/json', 'Connection': 'keep-alive'}
where True:
 print r.status_code

Related articles: