Question

求英语翻译啊，不要机翻，谢谢。

MCKUSICK I gather from the original GFS paper [Ghemawat, S., Gobioff, H., Leung, S-T. 2003. The Google File System. SOSP (ACM Symposium on Operating Systems Principles)] that file counts have been a significant issue for you right along. Can you go into that a little bit?
QUINLAN The file-count issue came up fairly early because of the way people ended up designing their systems around GFS. Let me cite a specific example. Early in my time at Google, I was involved in the design of the Logs Processing system. We initially had a model where a front-end server would write a log, which we would then basically copy into GFS for processing and archival. That was fine to start with, but then the number of front-end servers increased, each rolling logs every day. At the same time, the number of log types was going up, and then you’d have front-end servers that would go through crash loops and generate lots more logs. So we ended up with a lot more files than we had anticipated based on our initial back-of-the-envelope estimates.
This became an area we really had to keep an eye on. Finally, we just had to concede there was no way we were going to survive a continuation of the sort of file-count growth we had been experiencing.

Answer 1

MCKUSICK I gather from the original GFS paper [Ghemawat, S., Gobioff, H., Leung, S-T. 2003. The Google File System. SOSP (ACM Symposium on Operating Systems Principles)] that file counts have been a significant(重大的) issue for you right along. Can you go into that a little bit?
QUINLAN The file-count issue came up fairly early because of the way people ended up designing their systems around GFS. Let me cite(引用) a specific(特殊的) example. Early in my time at Google, I was involved(包含) in the design of the Logs Processing system. We initially had a model where a front-end server would write a log, which we would then basically(主要地) copy into GFS for processing and archival(档案的). That was fine to start with, but then the number of front-end servers increased, each rolling logs every day. At the same time, the number of log types was going up, and then you’d have front-end servers that would go through crash loops(环) and generate(形成) lots more logs. So we ended up with a lot more files than we had anticipated(预期) based on our initial back-of-the-envelope estimates(估计).
This became an area we really had to keep an eye on. Finally, we just had to concede(承认) there was no way we were going to survive(幸存) a continuation(继续) of the sort of file-count growth we had been experiencing.
————————————————————————————————————————————
麦库西克收集从原来的政府飞行服务队文[格玛沃特，美国，gobioff，小时，梁，s-t.2003。谷歌文件系统。sosp（操作系统原理会议）]，文件计数是一个重大的问题（重大的）你吧。你可以进入这一点吗？
昆兰的file-count问题上来比较早，因为人们的最终设计的系统围绕政府飞行服务队。让我举（引用）一个具体的例子（特殊的）。早在我的时间在谷歌，我参与（包含）在设计的日志处理系统。我们最初的模式，前端服务器会写日志，这我们就基本上（主要地）复制成队处理和档案（档案的）。这是好的开始，但数量增加的前端服务器，每个滚动记录每一天。同时，一些日志类型上，然后你就有前端服务器将通过碰撞循环（环）和生成（形成）更多的日志。所以我们结束了很多文件超过了我们的预期（预期）根据我们的初步粗略估计（估计）。
这成为我们真的不得不照看。最后，我们就不得不承认（承认）在那里没有办法进行下去（幸存）继续（继续）的排序file-count增长我们已经经历。

Answer 2

我收集的McKusick队从原来的文件[Ghemawat，Gobioff，H。，亮，意。 2003。 Google文件系统。 SOSP（ACM作业系统原理座谈会）]文件数已经为您的重要问题一起。你可以进入，一点点吗？
昆兰的文件数问题相当早，因为人结束了他们的系统设计围绕政府飞行服务队的方式上来。让我举一个具体的例子。早在我在谷歌的时候，我曾参与的原木加工系统的设计。最初，我们有一个模型，其中前端服务器将写入日志，然后我们基本上进入政府飞行服务队处理和档案复制。这是开始，但随后的前端服务器的数量增加，每个滚动记录的每一天。在同一时间，日志类型是去了，然后你不得不前端服务器将通过崩溃循环，并产生大量更多的日志。所以我们多了很多，比我们预期根据我们的初步文件结束了回来，信封估计。
这成为我们真的不得不保持一个眼睛上的一个区域。最后，我们不得不承认，有没有办法，我们要生存排序的文件数量的增长，我们经历的延续。