处理“速度”和限制 [英] Processing "speed" and limitations

查看:97
本文介绍了处理“速度”和限制的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您好,


我们目前正在将翻译文件从翻译记忆库系统(TMS)发送到Microsoft机器翻译。  时间限制为1小时,此时,如果机器翻译文件未返回TMS,则工作流程将出错。
 有没有人知道通过MT的单词或字符的典型吞吐量? -  


 即,我们希望在1小时内处理多少个单词/字符?  


处理速度是否取决于语言对? 


人们在MT处理速度方面会出现很大差异吗?  


感谢您提供任何见解。 


Gregg


 

解决方案

Gregg,


200字以内的请求平均处理约500毫秒,包括基于美国的网络延迟。



时间不随长度线性增加。请求最大值为10K字符。超时13秒。 13秒之后意味着你会得到回应,成功或失败。



流量可能会导致速度变化。


您尝试在1小时内访问的数据量是多少?


谢谢




Hello,

we're currently sending translation files from our Translation Memory System (TMS) to Microsoft Machine Translation.  There is a time limit of 1 hour, at which time, if the machine translated file is not returned to TMS, the workflow will error out.   Does anyone know the typical throughput of words or characters through the MT?- 

 Ie, how many words/characters could we expect to be processed in 1 hour?  

Is the processing speed dependent on the language pair? 

Do people experience large variance in processing speed with the MT?  

Thanks for any insights you may have. 

Gregg

 

解决方案

Gregg,

Requests under 200 characters are handled on average in ~500ms, including US-based network latency.

The time does not linearly increase with length. Request maximum is 10K characters. Timeout at 13 seconds. Means after 13 seconds you’ll get a response, success or failure.

Traffic might cause variance in speed .

What is the volume of data that you are trying to access in 1 hour?

Thank you


这篇关于处理“速度”和限制的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆