Concepts / Building Search UI / Improve performance
Feb. 21, 2019

Improve performance

You are reading the documentation for Angular InstantSearch v3, which is in beta. You can find the v2 documentation here.

Mitigate the impact of a slow network in your search application.

Algolia is a hosted search API. This means that if the network is slow, the search experience will be impacted. In this guide, you will see how to make the perception of search better even if the network shows some downtime.

Adding a loading indicator

Imagine a user using your search in a subway, by default this is the kind of experience they will get:

  • type some characters
  • nothing happens
  • still waiting, still nothing

At this point, the user is really wondering what is happening. You can start enhancing this experience by providing a visual element to hint that something is happening: a loading indicator.

The mechanism of the loading indicator is also available through custom widgets. Here we will make one that shows the text Loading… if the search request takes longer than expected:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
<!-- LoadingIndicator.ts -->
import { Component, Inject, forwardRef } from '@angular/core';
import { BaseWidget, NgAisInstantSearch } from 'angular-instantsearch';

const connectSearchMetaData = (renderFn, unmountFn) => (widgetParams = {}) => ({
  init() {
    renderFn({ searchMetadata: {} }, true);
  },
  render({ searchMetadata }) {
    renderFn({ searchMetadata }, false);
  },
  dispose() {
    unmountFn();
  },
});

@Component({
  selector: 'ais-loading-indicator',
  template: `
    <div>
      <div *ngIf="state.searchMetadata && state.searchMetadata.isSearchStalled">Loading...</div>
    </div>
  `,
})
export class LoadingIndicator extends BaseWidget {
  state: {
    searchMetadata: object;
  };

  constructor(
    @Inject(forwardRef(() => NgAisInstantSearch))
    public instantSearchParent
  ) {
    super('LoadingIndicator');
  }

  public ngOnInit() {
    this.createWidget(connectSearchMetaData as any, {});
    super.ngOnInit();
  }
}

This example shows how to make a custom component that writes Loading... when the search is stalled and nothing appears. Because of the delay introduced, users with optimal conditions will not be bothered by the message. If the user is not searching in those conditions, we provide some information about what is going on underneath.

Debouncing

Another way of thinking about performance perception is to try to prevent some of the lagging effect. The InstantSearch experience generates one query per keystroke. While this is normally desirable, in the worst of conditions this can lead to congestion because browsers can only make a limited amount of requests in parallel. By reducing the amount of requests done, we can prevent this effect.

Debouncing is a way to limit the number of requests and avoid processing non-necessary ones by avoiding sending requests before a timeout.

There is no built-in solution to debounce in Angular InstantSearch. You can implement it at the ais-search-box level with the help of the searchBox connector. Here is an example:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
import { Component, Inject, forwardRef, Input } from '@angular/core';
import { BaseWidget, NgAisInstantSearch } from 'angular-instantsearch';
import { connectSearchBox } from 'instantsearch.js/es/connectors';

@Component({
  selector: 'app-debounced-search-box',
  template: `
    <div>
      <input type="text" #input (keyup)="onChangeDebounced(input.value)" [value]="this.state.query">
    </div>
  `,
})
export class DebouncedSearchBox extends BaseWidget {
  private timerId = null;
  state: {
    query: string;
    refine: Function;
  };

  @Input() delay: number = 0;

  constructor(
    @Inject(forwardRef(() => NgAisInstantSearch))
    public instantSearchParent
  ) {
    super('DebouncedSearchBox');
  }

  public onChangeDebounced(value) {
    if (this.timerId) clearTimeout(this.timerId);
    this.timerId = setTimeout(() => this.state.refine(value), this.delay);
  }

  public ngOnInit() {
    this.createWidget(connectSearchBox, {});
    super.ngOnInit();
  }
}
1
 <app-debounced-search-box [delay]="200"></app-debounced-search-box>

You can find the source code on GitHub.

Optimize build size

Angular InstantSearch is by default optimized for build optimization like tree shaking. In order for the tree shaking to work effectively, refrain from importing NgAisModule. Instead import the modules you need individually.

Don’t do this:

1
2
3
4
5
6
import { NgAisModule } from 'angular-instantsearch';

@NgModule({
  imports: [NgAisModule.forRoot()],
})
export class AppModule {}

Do this instead:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
import {
  NgAisInstantSearchModule,
  NgAisHitsModule,
  NgAisSearchBoxModule,
} from 'angular-instantsearch';

@NgModule({
  imports: [
    NgAisInstantSearchModule.forRoot(),
    NgAisHitsModule,
    NgAisSearchBoxModule,
  ],
})
export class AppModule {}

Caching

Caching by default (and how to get rid of it)

By default, Algolia caches the search results of the queries, storing them locally in the cache. If the user ends up entering a search (or part of it) that has already been entered previously, the results will be retrieved from the cache, instead of requesting them from Algolia, making the application much faster.

While it is a very convenient feature, in some cases it is useful to have the ability to clear the cache and make a new request to Algolia. For instance, when changes are made on some records on your index, you might want the frontend side of your application to be updated to reflect that change (in order to avoid displaying stale results retrieved from the cache).

To do so, there is a function refresh available for custom connectors, which clears the cache and triggers a new search.

There are two different use cases where you would want to discard the cache:

  • your application data is being directly updated by your users (for example, in a dashboard). In this use case you would want to refresh the cache based on some application state such as the last modification from the user.

  • your application data is being updated by another process that you don’t manage (for example a CRON job that updates users inside Algolia). For this you might want to periodically refresh the cache of your application.

Refresh the cache triggered by an action from the user

If you know that the cache needs to be refreshed conditionally after a specific event, then you can trigger the refresh based on a user action (adding a new product, clicking on a button for instance).

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
import { Component, Inject, forwardRef } from '@angular/core';
import { BaseWidget, NgAisInstantSearch } from 'angular-instantsearch';

const connectRefresh = (renderFn, unmountFn) => (widgetParams = {}) => ({
  init() {
    renderFn({ refresh() {} }, true);
  },
  render({ instantSearchInstance }) {
    const refresh = instantSearchInstance.refresh.bind(instantSearchInstance);
    renderFn({ refresh }, false);
  },
  dispose() {
    unmountFn();
  },
});

@Component({
  selector: 'app-refresh',
  template: `
      <button (click)="state.refresh()"> Refresh </button>
  `,
})
export class Refresh extends BaseWidget {
  state: {
    refresh: Function;
  };

  constructor(
    @Inject(forwardRef(() => NgAisInstantSearch))
    public instantSearchParent
  ) {
    super('Refresh');
  }

  public ngOnInit() {
    this.createWidget(connectRefresh as any, {});
    super.ngOnInit();
  }
}

And use it within your app:

1
<app-refresh></app-refresh>

You can find the source code on GitHub.

Refresh the cache periodically

You also have the option to set up a given period of time that will determine how often the cache will be cleared. This method will ensure that the cache is cleared on a regular basis. You should use this approach if you cannot use a user action as a specific event to trigger the clearing of the cache.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
import { Component, Inject, forwardRef } from "@angular/core";
import { BaseWidget, NgAisInstantSearch } from 'angular-instantsearch';

const connectRefresh = (renderFn, unmountFn) => (widgetParams = {}) => ({
  init() {
    renderFn({ refresh() {} }, true);
  },
  render({ instantSearchInstance }) {
    const refresh = instantSearchInstance.refresh.bind(instantSearchInstance);
    renderFn({ refresh }, false);
  },
  dispose() {
    unmountFn();
  },
});

@Component({
  selector: 'app-refresh-periodically',
  template: ``,
})
export class RefreshPeriodically extends BaseWidget {
  state: {
    refresh: Function;
  };

  private timerId = null;
  @Input() delay: number = 10000;

  constructor(
    @Inject(forwardRef(() => NgAisInstantSearch))
    public instantSearchParent
  ) {
    super('RefreshPeriodically');
  }

  public ngOnDestroy(): void {
    if (this.timerId) {
      clearInterval(this.timerId);
    }
    super.ngOnDestroy();
  }

  public ngOnInit() {
    this.createWidget(connectRefresh as any, {});

    this.timerId = setInterval(() => {
      this.state.refresh();
    }, this.delay);

    super.ngOnInit();
  }
}

then use it as

1
<app-refresh-periodically [delay]="10000"></app-refresh-periodically>

Note that if you need to wait for an action from Algolia, you should use waitTask to avoid refreshing the cache too early.

Queries Per Second (QPS)

With Algolia, search operations are not part of any quota and will not be charged in any way. That being said, they are limited by the maximum QPS (the allowed number of queries performed per second) of the plan.

Every time you press a key in InstantSearch using the SearchBox, we count one operation. Then, depending on the widgets you will be adding to your search interface, you may have more operations being counted on each keystroke. For example, if you have a search made out of a ais-search-box, a ais-menu, and a ais-refinement-list, then every keystroke will trigger one operation. But as soon as a user refines the ais-menu or ais-refinement-list, it will trigger a second operation on each keystroke.

A good rule to keep in mind is that most search interfaces using InstantSearch will trigger one operation per keystroke. Then every refined widget (clicked widget) will add one more operation to the total count.

In case you have issue with the QPS you can consider implement a debounced ais-search-box.

Did you find this page helpful?