HTTP connections are not being reused in single threaded application

[meschbach]

While processing a large number of documents ( >40K) quickly with a single threaded application on ruby 2.2.3 the pool of ephemeral ports was exhausted. From my analysis a new connection appears to be created for each request to the Couch instance, leaving a large number of sockets in TIME_WAIT under Linux. After reading through CouchRest and HTTPClient I couldn't find any options or code to deal with KeepAlive or Pipe Lining. Did I overlook an option in the documentation?

[samlown]

@meschbach just catching up with this. I'm assuming you're using the beta release of couchrest with httpclient? If so, how are you performing the requests?

The HTTP connections should be handled by the HTTPClient library, but it does require that you use a shared database object, i.e.:

server = CouchRest.new
db = server.database!('testdb')
db.get("SOMEID")