From c938c59af617bcea4ed3ed1d6de198dce6286087 Mon Sep 17 00:00:00 2001 From: Andrew Kane Date: Sun, 15 Jan 2017 21:47:21 -0800 Subject: [PATCH] queues -> queuing [skip ci] --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index bc7b697..0af34fc 100644 --- a/README.md +++ b/README.md @@ -470,9 +470,9 @@ There are four strategies for keeping the index synced with your database. And [install Active Job](https://github.com/ankane/activejob_backport) for Rails 4.1 and below. Jobs are added to a queue named `searchkick`. -3. Queues +3. Queuing - Push ids of records that need updated to a queue and reindex in the background in batches. This is more performant than the asynchronous method, which updates records individually. See [how to use](#queues). + Push ids of records that need updated to a queue and reindex in the background in batches. This is more performant than the asynchronous method, which updates records individually. See [how to set up](#queuing). 4. Manual @@ -1293,7 +1293,7 @@ And use: Searchkick.reindex_status(index_name) ``` -### Queues +### Queuing You can also queue updates and do them in bulk for better performance. First, set up Redis in an initializer. -- libgit2 0.21.0