[GitHub] [tinkerpop] krlawrence commented on pull request #1298: [DRAFT] TINKERPOP-2352 reduce Python driver default pool sizes to 1

[GitBox <gi...@apache.org>]

krlawrence commented on pull request #1298:
URL: https://github.com/apache/tinkerpop/pull/1298#issuecomment-644132867


   I am not sure I agree that "most" Python Gremlin apps are single threaded. Just because Python has the Global Interpreter Lock (GIL) does not mean that the threading library is not effective in I/O bound scenarios. I regularly write Python Gremlin apps that have anywhere from 8 to 96 threads. Because requests to a Gremlin Server tend to be I/O bound the Python threading library actually works well as threads will naturally block while waiting for I/O. Rather than change these defaults I think a better solution might actually be to add as needed to the documentation giving specific examples of where different configurations make sense and include code examples of how to set those configurations up. I am aware of many good use cases for each. Here are just two cases
   
   1. A client doing a lot of writes across multiple threads from a container/API server etc. (multiple threads definitely help here).
   
   2. An AWS Lambda function where it makes sense to have just 1 connection as you can think of a Lambda as being a thread in that context.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org