Concurrent operation scheduler

[jarreds]

In the spirit of optimized batching, I've been playing around with a coroutine implementation in Golang that allows cooperative multitasking to batch IO. I can share more details on that as the experiment progresses.

This is the code I used to shim in a new "scheduler" for gqlgen. Creating as draft for now until it proves out that there is actually reason to have this code.

[coveralls]

coverage: 73.832% (-0.08%) from 73.915%
when pulling 569c57b on jarreds:operation-scheduler
into 3fc5a53 on 99designs:master.

[StevenACoffman]

Interesting! I'm very curious to learn what you find out!

However, I would suggest that in the Dispatch you really need the scheduler bypass when you only have a single task. Having this case where it doesn't go through a scheduler or anything complicated is an important performance feature for a surprising number of use cases. Every time we've removed it, there's been a storm of complaints.

func (m *FieldSet) Dispatch(ctx context.Context) {
	if len(m.delayed) == 1 {
		// only one concurrent task, no need to spawn a goroutine or deal create waitgroups

[jarreds]

Noted! FWIW I did put a special case in the default goroutine scheduler to run len one tasks (w/o wait groups) and the last f "on-thread:" https://github.com/99designs/gqlgen/pull/3468/files#diff-3a919dfc5028540a932a129e10b6e9cb749a1fd70be686dc7471ff440d823086R37-R40

So it should launch the minimal number of goroutines like it did before.