# Batch Remove (AER-6499)

**URL:** <https://discuss.aerospike.com/t/batch-remove-aer-6499/425>\
**Category:** Delivered Requests\
**Created:** [September 26, 2014, 4:01am UTC](https://discuss.aerospike.com/t/batch-remove-aer-6499/425 "2014-09-26T04:01:27Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hanson](https://avatars.discourse-cdn.com/v4/letter/h/9e8a1a/32.png) [@Hanson](https://discuss.aerospike.com/u/Hanson)\
**Post date:** [September 26, 2014, 4:01am UTC](https://discuss.aerospike.com/t/batch-remove-aer-6499/425/1 "2014-09-26T04:01:27Z")

</div>

Aerospike can support Batch Get: [http://www.aerospike.com/apidocs/c/db/dd9/group\_\_batch\_\_operations.html](http://www.aerospike.com/apidocs/c/db/dd9/group __batch__ operations.html)

How about to support Batch Remove?

---

<div class="post-metadata">

**Author:** ![wchu](https://avatars.discourse-cdn.com/v4/letter/w/a5b964/32.png) [@wchu](https://discuss.aerospike.com/u/wchu)\
**Post date:** [September 28, 2014, 5:02am UTC](https://discuss.aerospike.com/t/batch-remove-aer-6499/425/2 "2014-09-28T05:02:36Z")

</div>

Hi Hanson, Currently batch write/remove is not supported.

---

<div class="post-metadata">

**Author:** ![Hanson](https://avatars.discourse-cdn.com/v4/letter/h/9e8a1a/32.png) [@Hanson](https://discuss.aerospike.com/u/Hanson)\
**Post date:** [September 28, 2014, 5:37am UTC](https://discuss.aerospike.com/t/batch-remove-aer-6499/425/3 "2014-09-28T05:37:30Z")

</div>

Any plan to support Batch Remove?

---

<div class="post-metadata">

**Author:** ![bbulkow](https://avatars.discourse-cdn.com/v4/letter/b/779978/32.png) [@bbulkow](https://discuss.aerospike.com/u/bbulkow)\
**Post date:** [October 3, 2014, 7:46pm UTC](https://discuss.aerospike.com/t/batch-remove-aer-6499/425/4 "2014-10-03T19:46:30Z")

</div>

Yes, we’ll do all of the batch calls shortly - sorry I can’t be more specific - not in the next few months.

Honestly, most people get excited about the batch calls, but if you can deal with a simple async framework for your application that spins the requests in parallel (like using node or Jetty or Go coroutines), you’ll find Aerospike outperforms most systems in batch mode.

Of course, having a simple API is a good thing…

---

<div class="post-metadata">

**Author:** ![Hanson](https://avatars.discourse-cdn.com/v4/letter/h/9e8a1a/32.png) [@Hanson](https://discuss.aerospike.com/u/Hanson)\
**Post date:** [October 8, 2014, 8:58am UTC](https://discuss.aerospike.com/t/batch-remove-aer-6499/425/5 "2014-10-08T08:58:57Z")

</div>

Thanks for the feedback.

I expect the Batch Remove is done on server side with a single request from client to server, instead of a simple wrapper of client API to send multiple Remove requests. The purpose is for performance: to reduce total latency and CPU cost on both client and server.

---

<div class="post-metadata">

**Author:** ![dragon](https://avatars.discourse-cdn.com/v4/letter/d/13edae/32.png) [@dragon](https://discuss.aerospike.com/u/dragon)\
**Post date:** [January 13, 2015, 7:53pm UTC](https://discuss.aerospike.com/t/batch-remove-aer-6499/425/6 "2015-01-13T19:53:13Z")

</div>

Does using the new Async client and calling the delete call in a loop same as calling delete function in parallel using some kinda async framework?

Thanks.

---

<div class="post-metadata">

**Author:** ![wchu](https://avatars.discourse-cdn.com/v4/letter/w/a5b964/32.png) [@wchu](https://discuss.aerospike.com/u/wchu)\
**Post date:** [January 14, 2015, 9:15pm UTC](https://discuss.aerospike.com/t/batch-remove-aer-6499/425/7 "2015-01-14T21:15:59Z")

</div>

I assume you are asking about the current single-record delete functionality. Yes, they would both be using the same record-delete call on the server side. The difference is purely on the client calling model.

---

<div class="post-metadata">

**Author:** ![dragon](https://avatars.discourse-cdn.com/v4/letter/d/13edae/32.png) [@dragon](https://discuss.aerospike.com/u/dragon)\
**Post date:** [January 15, 2015, 4:57pm UTC](https://discuss.aerospike.com/t/batch-remove-aer-6499/425/8 "2015-01-15T16:57:09Z")

</div>

Thanks wchu for reply.

I was actually confused about difference in calling using normal client and async client. As per my understanding, calling using Async client will not wait for the response however normal client call will. Is that right?

Regards.

---

<div class="post-metadata">

**Author:** ![wchu](https://avatars.discourse-cdn.com/v4/letter/w/a5b964/32.png) [@wchu](https://discuss.aerospike.com/u/wchu)\
**Post date:** [January 16, 2015, 4:38am UTC](https://discuss.aerospike.com/t/batch-remove-aer-6499/425/9 "2015-01-16T04:38:36Z")

</div>

You must be talking about the Java/C# client?

These Async calls are purely client side constructs, where the read/write requests are made none-blocking by putting the request on a queue, thus freeing up the calling thread.

Hope this helps.

---

<div class="post-metadata">

**Author:** ![kporter](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/kporter/32/515_2.png) [@kporter](https://discuss.aerospike.com/u/kporter)\
**Post date:** [June 9, 2022, 11:02pm UTC](https://discuss.aerospike.com/t/batch-remove-aer-6499/425/10 "2022-06-09T23:02:35Z")

</div>

The “batch writes/deletes/UDFs” feature has been released in [Aerospike 6.0.0.0](https://download.aerospike.com/download/server/notes.html#6.0.0.0).

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/system/32/2274_2.png) [@system](https://discuss.aerospike.com/u/system)\
**Post date:** [September 1, 2022, 11:02pm UTC](https://discuss.aerospike.com/t/batch-remove-aer-6499/425/11 "2022-09-01T23:02:48Z")

</div>

Closed on September 1, 2022, 11:02pm UTC

This topic was automatically closed 84 days after the last reply. New replies are no longer allowed.
