Apologies, I missed the last response. I've created an issue to track this. https://github.com/grpc/grpc/issues/13536
On Monday, November 27, 2017 at 10:16:00 PM UTC-8, [email protected] wrote: > > Hi Ken, > > Is there an issue to track the progress of this? > > On Tuesday, August 1, 2017 at 4:20:33 PM UTC-7, Ken Payson wrote: >> >> There is some work underway to support a prefork based process pool for >> Python. >> I'd recommend avoiding using fork altogether with gRPC until it is >> available. >> >> On Wednesday, July 19, 2017 at 11:20:24 PM UTC-7, [email protected] wrote: >>> >>> Hello. >>> I need of process-based pooling. >>> >>> My use case is preloading initialized large memory like zygote process. >>> >>> In this case, process-based pooling has two merits >>> - skip Initialization processing. >>> - do not want to have duplicate memory in process. >>> >>> But I did not know where to patch. >>> As an alternative I'm thinking about forking from a thread but is it >>> safe? >>> >>> Best regards, >>> >>> >>> 2017年1月6日金曜日 23時38分32秒 UTC+9 [email protected]: >>>> >>>> Just wanted to add another voice who is in need of process-based >>>> pooling, for the same reasons as Stefan mentions in his use case. >>>> >>>> Thanks, >>>> Steve >>>> >>> -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/44af1c19-4820-4516-ade6-7cb4ed2da7c8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
