About the speed of "Do a search for"

[fujiwara.enc]

Hello.

Currently, I have created a database called “Knowledge_Question” and call “Knowledge_Question” from there with “Do a search for”.

I then use “filtered” to control the data displayed depending on the search conditions.

While I’m running this, I receive a request from a client saying, “The list screen is displaying slowly, so I would like you to improve the speed.”

How can we improve the speed of “Do a search for”?

For reference, I will provide you with the screen, database, and contents of “Knowledge_Question”.

“Knowledge_Question” Fields1

“Knowledge_Question” Fields2

"Knowledge_Question"Number of data

“Knowledge_Question” Do a search for

“Knowledge_Question” Do a search for filtered

“Knowledge_Question” Conditinal

[georgecollier]

@fujiwara.enc

スクリーンショット 2024-11-08 1525591292×1198 134 KB

Advanced filters are performed wholly client side, which is at least one reason it would be slow. What are they filtering for?

[fujiwara.enc]

We use filtered to make this search possible.

From the top,

Target tenant

Knowledge category

Solution possibility classification

Poster

Knowledge title

Knowledge content

[georgecollier]

Are you not able to add them as constraints in ‘Do a search for’?

[GH5T]

Make sure you’re caching/storing the data first before applying filters/queries. Otherwise, it’ll run slow (runs each filter as requested multiple times, rather than querying the same data source again).

[fujiwara.enc]

When adding it as a constraint for ‘Do a search for’, you can only create a conditional expression such as “when XX and XX”,
so I want to create a conditional expression such as “when XX or XX”, so I’m using filter.

[fujiwara.enc]

Where should I check to ensure that it is caching/saving data?

[georgecollier]

@fujiwara.enc

“when XX or XX”, so I’m using filter.

You can use a merged search as an OR condition (search with condition 1:merged with search with condition 2)

[fujiwara.enc]

If you merge, it will become “Search for XXs merged with Search for XXs”, and you will have to use ‘Do a search for’ multiple times, so won’t that make processing even heavier?

[ihsanzainal84]

Backend search (using constraints) is more performant. Forcing heavy client side filtering will kill browser performance for your users.

[fujiwara.enc]

What exactly does back-end search do?

[ihsanzainal84]

I meant using constraints in your “Search for”.