UC知道计算机论文的翻译
来源：百度知道 编辑：UC知道 时间：2024/05/30 01:45:16
各位高手，本人最近有篇论文要翻译，请各位帮帮忙！
The architectural limitation for no more than 64k database files in a federation meant that very large files were used, particularly for the raw and reconstructed data where 20GB files were used. This had adverse operational impact, both at SLAC, but also in terms of data distribution to remote sites. The use of such large database files also meant that events from many different runs were mixed together within database files, causing the distribution of event samples to remote sites to also be inefficient.
• The architectural limitation on a single federation limited to 64k database files meant that there was no way of scaling to multiple petabytes of data, as was expected to be generated over the lifetime of the experiment.
• Correlated with the creation of large databases, some of the smaller databases used many containers, and scaling problems were seen when the number of containers in a database became a significan
The architectural limitation for no more than 64k database files in a federation meant that very large files were used, particularly for the raw and reconstructed data where 20GB files were used. This had adverse operational impact, both at SLAC, but also in terms of data distribution to remote sites. The use of such large database files also meant that events from many different runs were mixed together within database files, causing the distribution of event samples to remote sites to also be inefficient.
• The architectural limitation on a single federation limited to 64k database files meant that there was no way of scaling to multiple petabytes of data, as was expected to be generated over the lifetime of the experiment.
• Correlated with the creation of large databases, some of the smaller databases used many containers, and scaling problems were seen when the number of containers in a database became a significan
建筑限制不超过64k档案数据库意味着一个很大联邦档案用 特别是对原始数据、改档案而采用20GB 这一业务造成负面影响 在塌陷 而且在数据分配到偏僻地点 使用这种大型档案数据库也意味着从许多不同的挤提事件混合一起档案数据库 造成样本分布在偏远地点活动,也不得力
建筑限制联邦局限于单一档案数据库64k意味着根本无从结垢多重饿鬼字节数据 由于预期寿命超过产生实验
与大型数据库的建立,一些规模较小的数据库采用多结垢问题主要出现在一些重大的容器在数据库成了建筑限分数32K条
网上吞吐量迅速重建(OPR)的农场加工和服务器节点负责伪实时数据重建活动的客观性是有限的饱和锁定服务器2 这限制了农民的100Hz吞吐量为150处理节点 大部分的锁被定为交通服务器相关数据库缩放容器内