Add concurrent for with method

[sinhnv1991]

can Laravel help add support withConcurrent method or other if use laravel octance get data of relations, example: Book::withConcurrent(['categories', 'author'])->get();?

[macropay-solutions]

@sinhnv1991
See this related thread #55316

We tried with curl_multi_init and we had to do them in 2 chunks when the relations number is over 12 for example because the time lost with additional things was greater than the time spared by the sqls running in parallel async. Also the cpu and memory spikes were an issue.

The tricky part was getting the sql because it was not the same as the toSql() returned.

But anyway, it could be implemented also via concurrency but it would need testing with big volumes of data.

[sinhnv1991]

@macropay-solutions
if we run sql first for book and extract ids of book, we can add run concurrent for categories and author by example [$categories, $auths] = Concurrency::run([
fn () => DB::table('categories')->whereIn('id', $idsCategoryFromBook)->get(),
fn () => DB::table('auth')->whereIn('id', $idsUserIdFromBook)->get(),
]); and can map again to relation of books, and categories if have relations like brands we can add new concurrent get brands by extract ids categories and we can getting all the sql of main queries and relations right?

[macropay-solutions]

It is no that simple. You have many types of relations + scopes. Throwing an exception in statement prepared event gives you the exact query needed to be executed for each relation. (We did not handle morph relations).

Also mapping the resulting array depending on its relation type, in each model is a challenge.

[sinhnv1991]

I think like default with laravel query relation and mapping data again we only need add Concurrency::run to default laravel relations query code, doest need change more every things

[sinhnv1991]

Im not sure, but i will try

[macropay-solutions]

I think like default with laravel query relation and mapping data again we only need add Concurrency::run to default laravel relations query code, doest need change more every things

Maybe you will understand better what we said once you step on the same footprints as we did by implementing it (but we did it to work retroactively, not only on the latest versions.