Replies: 1 comment 9 replies
-
Hi @gfd2020, that's a good idea! Actually we do a similar thing with simultaneous containers expansion, at some point we limited it to half the number of CPU cores, other containers are re-enqueued. We could do something similar to audios. But this should be Configurable. If your transcription cluster is slow, clients could be very idle and could do other things. If the cluster is very fast, our case, decreasing the number of simultaneous transcription requests can waste the cluster resources and may decrease the overall throughput. To know if there are other types of files different than audios in the queue is another challenge, we don't have this info today, not sure how to do this... |
Beta Was this translation helpful? Give feedback.
-
Remote audio transcription with the IPED server/client is excellent. It helps a lot in this difficult task.
However, I noticed something that could perhaps improve performance a little.
For example: a UFDR report has photos, spreadsheets, chats, audio, etc. When the client identifies audio it will send it to the remote server. But sometimes it uses all threads to send to the server, so it remains idle and waiting for the result. Perhaps we could configure a maximum number of transcription threads if it have other types of files not yet processed (maybe half), so as not to leave the client inactive and doing other tasks.
Beta Was this translation helpful? Give feedback.
All reactions