Am 13.08.2014 um 12:08 hat Ming Lei geschrieben:
> This test runs dummy function with coroutine by using
> two enter and one yield since which is a common usage.
>
> So we can see the cost introduced by corouting for running
> one function, for example:
>
> Run operation 2000 iterations
Hi Guys,
On Wed, Aug 13, 2014 at 6:08 PM, Ming Lei wrote:
> This test runs dummy function with coroutine by using
> two enter and one yield since which is a common usage.
>
> So we can see the cost introduced by corouting for running
> one function, for example:
>
> Run operation 2000
On Wed, Aug 13, 2014 at 10:27 PM, Benoît Canet wrote:
> The Wednesday 13 Aug 2014 à 18:08:47 (+0800), Ming Lei wrote :
>> This test runs dummy function with coroutine by using
>> two enter and one yield since which is a common usage.
>>
>> So we can see the cost introduced by corouting for running
On 13 août 2014 16:27:29 CEST, "Benoît Canet" wrote:
> The Wednesday 13 Aug 2014 à 18:08:47 (+0800), Ming Lei wrote :
> > This test runs dummy function with coroutine by using
> > two enter and one yield since which is a common usage.
> >
> > So we can see the cost introduced by corouting for r
The Wednesday 13 Aug 2014 à 18:08:47 (+0800), Ming Lei wrote :
> This test runs dummy function with coroutine by using
> two enter and one yield since which is a common usage.
>
> So we can see the cost introduced by corouting for running
> one function, for example:
>
> Run operation 2
This test runs dummy function with coroutine by using
two enter and one yield since which is a common usage.
So we can see the cost introduced by corouting for running
one function, for example:
Run operation 2000 iterations 4.841071 s, 4131K operations/s
242ns per coroutine
