Hi Vijay, Just confirming that FIFO ordering of immediately-firing alarms is guaranteed by the complete_queue. Right?
-Sumant On Friday, February 8, 2019 at 8:10:39 AM UTC-8, [email protected] wrote: > > Hi Vijay, > > 3,000,000 per second rocks! > Thx much everyone! > > Regards, > Sumant > > On Thursday, February 7, 2019 at 8:43:53 AM UTC-8, Vijay Pai wrote: >> >> I just created a pull request to benchmark immediately-firing alarms. The >> results on my Mac laptop suggest that you can fire at least >> 3,000,000 immediate alarms per second on a single thread, so I don't think >> you'll hit a limit from that. >> >> I would strongly advise against directly using >> grpc_cq_begin_op/grpc_cq_end_op . Those are internal functions and will >> change name/behavior whenever we choose. >> >> I should have some more information to announce on the callback API >> within the next few weeks but we continue to prepare it for >> production-readiness in both unary and streaming cases. >> >> - Vijay >> >> -- 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/98abb701-1b90-4c2f-87ea-821b83d17564%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
