# Asynchronous operations

**URL:** <https://discuss.pennylane.ai/t/asynchronous-operations/36>\
**Category:** PennyLane Development\
**Created:** [November 23, 2018, 12:40pm UTC](https://discuss.pennylane.ai/t/asynchronous-operations/36 "2018-11-23T12:40:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Christian\_Gogolin](https://avatars.discourse-cdn.com/v4/letter/c/91b2a8/32.png) [@Christian\_Gogolin](https://discuss.pennylane.ai/u/Christian_Gogolin)\
**Post date:** [November 23, 2018, 12:40pm UTC](https://discuss.pennylane.ai/t/asynchronous-operations/36/1 "2018-11-23T12:40:39Z")

</div>

There are some obvious cases where PennyLane could parallelize the execution on quantum devices, such as the computation of gradients.

Due to memory constrains it might not be a good idea to compute the expectations that are needed to compute a gradient in parallel when a simulator is used, but when a hardware backend is in use, it would be good to queue all the 2_n_shots many device runs to compute n gradients all at once instead of doing 2\*n sequential calls to the quantum hardware.