Queues are intended to group documents on which users must perform some kind of task or review.
The first thing to ask yourself is whether you are using a glue properly.
Athento recommends NOT to use queues to group more than 200 documents. For larger groupings, you should use reports.
There are several product mechanisms to improve the loading of a queue. We review them below.
Activate the queue against Elastic Search
The default queue queries are performed against the database. If your instance has integration with Elastic Search, we recommend that you request the activation of this functionality that allows queries to be performed against Elastic Search and not against the database.
The support team will help you.
Activate a queue against Elastic Search
En el funcionamiento por defecto de las colas, cada que un usuario accede a una (o al dashboard si ésta se encuentra publicada en él) se realiza una consulta contra la base de datos. Cuantos más usuarios consulten las colas y más documentos tengas estas, mayor será el consumo de recursos del sistema.
If your queue has a volume of more than 200 documents and you do not have Elastic Search, you may consider using an offline queue. An offline queue is updated only once for all users. It is possible to schedule its update several times a day.
Please note before requesting the activation of this functionality that:
- Offline queues are not updated in real time. If the documents in a queue are constantly changing, it is not a good idea to use this type of queue.
- Do not activate this option in trays that have filtering by user.
Please sign in to leave a comment.