# Actorpool pipelining **URL:** \ **Category:** Ray Core\ **Created:** [May 27, 2023, 1:52am UTC](https://discuss.ray.io/t/actorpool-pipelining/10805 "2023-05-27T01:52:23Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![kentropy](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/kentropy/32/4491_2.png) [@kentropy](https://discuss.ray.io/u/kentropy)\ **Post date:** [May 27, 2023, 1:52am UTC](https://discuss.ray.io/t/actorpool-pipelining/10805/1 "2023-05-27T01:52:23Z")
**How severe does this issue affect your experience of using Ray?** - Low: It annoys or frustrates me for a moment. With Ray tasks, we can easily pass object references around to build pipelines. However, it seems unnatural to do this with Ray actors. After some research, it seems that actor pool is the only way to load balance actor resources (e.g., use 10 actors to read and process 1000 data). However, actor pool get methods returns ray.get() instead of future or promises, which denies potential downstream pipeline. A possible solution is to just initiate 1000 actors and make use of the scheduler? Is there something missing here, or is there other patterns to use in this type of scenario? ---
**Author:** ![jjyao](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/jjyao/32/1799_2.png) [@jjyao](https://discuss.ray.io/u/jjyao)\ **Post date:** [May 30, 2023, 4:42pm UTC](https://discuss.ray.io/t/actorpool-pipelining/10805/2 "2023-05-30T16:42:18Z")
Could you elaborate the pipelining you want to do? Also you don’t have to use the ray actor pool util, you can easily write your own actor pool that serves your purpose. ---
**Author:** ![kentropy](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/kentropy/32/4491_2.png) [@kentropy](https://discuss.ray.io/u/kentropy)\ **Post date:** [June 19, 2023, 2:04pm UTC](https://discuss.ray.io/t/actorpool-pipelining/10805/3 "2023-06-19T14:04:57Z")
Sorry for late replies. Thank you for replying. I think my problem can be solved by modifying actorpool.