XML

Word

Printable

Details

Type: Bug
Resolution: Fixed
Fix Version/s: translate5 - 6.0.0, translate5 - 6.1.0
Affects Version/s: None
Component/s: Main back-end mechanisms (Worker, Logging, etc.), SpellCheck (LanguageTool integration), TermTagger integration

Urgency:
High
ChangeLog Description:

Hide
translate5 - 6.0.0:
Improvement: TermTagger Worker & SpellCheck Worker are not queued dynamically anymore but according to the configured slots & looping through segments. This reduces deadlocks & limits processes
translate5 - 6.1.0:
Improve behavior of Processing-State queries regarding deadlocks

Show
translate5 - 6.0.0: Improvement: TermTagger Worker & SpellCheck Worker are not queued dynamically anymore but according to the configured slots & looping through segments. This reduces deadlocks & limits processes translate5 - 6.1.0: Improve behavior of Processing-State queries regarding deadlocks
Checklist:

Empty

show more show less

Description

problem

currently on termtagging and spellchecking a lot of workers are produced (segment count / 5) * slotcount.

This produces a lot of overhead and DB load in worker organization, also 5 task with 5 minutes per each import, will all be finished after 25 minutes.

solution

Change that, only one TermTagger/SpellCheck Worker per slot is created, and each worker loops over the available segments until all segments are done.

Attachments

Sub-Tasks

1.	Own worker-type "Resource/Service Worker"		Done	Axel Becher
2.	Required changes in worker architecture to improve performance of multiple Request based AutoQA workers		Done	Axel Becher

Activity

People

Assignee:: Axel Becher

Reporter:: Thomas Lauria

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 16/Sep/2022 02:19

Updated:: 09/May/2024 09:53

Resolved:: 30/Mar/2023 01:06