You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the query is passed to the function, it will do a Promise.all() of all rooms, which might cause the problem that we've been fighting for a long time, the grpc issue. So I think we need to use batch operation for this method to avoid the grpc problem.
The text was updated successfully, but these errors were encountered:
I'm planning to use async pool or iterator worker or p-map to implement a Promise.all() with a concurrency limitation for a better performance.
huan
changed the title
roomSearch using Promise.all might cause hostie connection issue
Promise.all with concurrency limitation implementation
Aug 17, 2021
Related to wechaty/puppet-service#31
Currently the code logic for
roomSearch
inwechaty-puppet
is not using batch operation, like below:https://github.com/wechaty/wechaty-puppet/blob/804b31b970e931547238d59de43847178a2869cd/src/puppet.ts#L1174-L1212
When the
query
is passed to the function, it will do aPromise.all()
of all rooms, which might cause the problem that we've been fighting for a long time, the grpc issue. So I think we need to use batch operation for this method to avoid the grpc problem.The text was updated successfully, but these errors were encountered: