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/d6f3157d-6801-48d2-a044-a6e9b210d25e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
