Question about coroutine

[MoJI4yH]

I tried to compare the work of the coroutines in golang and "may" library, using the example of simple code that does almost nothing except run these coroutines

In go

package main

import (
	"sync"
	"time"
)

func main() {
	var wg sync.WaitGroup
	start := time.Now();
	for i := 0; i <= 10000000; i++ {
		wg.Add(1);
		go func() {
			wg.Done()
		}()
	}
	wg.Wait()
	finish := time.Now();
	elapsed := finish.Sub(start)
	println(elapsed.Seconds())
}

and it take about 3-4 sec

but if i run this

#[macro_use]
extern crate may;

use std::time::{Instant};
use wg::WaitGroup;

fn main() {
    let wg = WaitGroup::new();

    let now = Instant::now();
    
    for _ in 0..10_000_000 {
    let co_wg = wg.add(1);
    go!(move || {
    co_wg.done();
    });
    }
    
    wg.wait();
    println!("{}", now.elapsed().as_secs());
}

it take about 60+ sec

maybe I don't understand something or "may" is not designed to run millions coroutines at one time

[Xudong-Huang]

the wg::WaitGroup is not a may compatible API

…

________________________________ 发件人: Shundrov Vitaly ***@***.***> 发送时间: 2023年5月21日 8:35 收件人: Xudong-Huang/may ***@***.***> 抄送: Subscribed ***@***.***> 主题: [Xudong-Huang/may] Question about corutine (Issue #103) I tried to compare the work of the coroutines in golang and "may" library, using the example of simple code that does almost nothing except run these coroutines In go ` package main import ( "sync" "time" ) func main() { var wg sync.WaitGroup start := time.Now(); for i := 0; i <= 10000000; i++ { wg.Add(1); go func() { wg.Done() }() } wg.Wait() finish := time.Now(); elapsed := finish.Sub(start) println(elapsed.Seconds()) } ` and it take about 3-4 sec but if i run this ` #[macro_use] extern crate may; use std::time::{Instant}; use wg::WaitGroup; fn main() { let wg = WaitGroup::new(); let now = Instant::now(); for _ in 0..10_000_000 { let co_wg = wg.add(1); go!(move || { co_wg.done(); }); } wg.wait(); println!("{}", now.elapsed().as_secs()); } ` it take about 60+ sec maybe I don't understand something or "may" is not designed to run millions coroutines at one time ― Reply to this email directly, view it on GitHub<#103>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADLGBK7VZ776TKJ6DPTPFW3XHFPNBANCNFSM6AAAAAAYJBIP2Q>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Xudong-Huang]

I would support may::sync::WaitGroup and may::sync::Barrier in future release