fix: use _max_concurrent_semantic in Semantic queue worker

[vincent067]

Summary

Fixes #873

The _max_concurrent_semantic variable was stored in QueueManager.__init__ and passed to SemanticProcessor, but it was not used when starting the Semantic queue worker thread.

Problem

In _start_queue_worker:

max_concurrent = self._max_concurrent_embedding if queue.name == self.EMBEDDING else 1  # Hardcoded to 1!

This caused the Semantic queue to always have max_concurrent = 1, ignoring the configured vlm.max_concurrent value for queue-level concurrency.

Solution

max_concurrent = self._max_concurrent_embedding if queue.name == self.EMBEDDING else self._max_concurrent_semantic

Impact

Users can now configure Semantic queue concurrency through ov.conf, enabling faster processing when there are many pending Semantic tasks.

Thanks for the great bug report! 👍

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Li Wenjun seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

Failed to generate code suggestions for PR