|
发表于 2005-8-29 18:17:21
|
显示全部楼层
####################################################################
I run Linux (2.6.x kernel). E@H doesn't show up when running "top". Is it doing anything?
--------------------------------------------------------------------
Please see the following. It applies to us because Einstein@Home is a multi-threaded application.
请看后面一个问题和解答。由于Einstein@Home是一个多线程的程序,所以下面的解答也适用。
####################################################################
Question: Why is %CPU underreported for multi-threaded (Java, etc.) apps?
--------------------------------------------------------------------
Answer: You need to upgrade to the 2.6.10 kernel at least. Older kernels do not provide a reasonable way to get this information.
您需要把您的内核升级到至少2.6.10。旧的内核没有一个很好的途径去获取这个信息。
[BA]
####################################################################
I am running MacOS 10.x (x<3). Why do all my results end up with "Client Error"?
--------------------------------------------------------------------
BOINC and thus Einstein@Home requires MacOS 10.3 (Darwin 7.3) or later.
BOINC和Einstein@Home客户端需要MacOS 10.3 (Darwin 7.3)或以上的操作系统。
####################################################################
How can I see the progress (percentage done etc.) running a comand line client (Mac, Linux)?
--------------------------------------------------------------------
This information is kept in the file client_state.xml in the fraction_done tag.There are third party tools that read it. If you want to have a quick look, open a Terminal, cd to the boinc directory and grep for fraction done:
进度信息储存在client_state.xml的fraction_done标志中。有第三方的软件可以阅读它。如果您想很快地看一看,可以打开一个终端,进入BOINC的目录,搜索字符串fraction_done。
cd BOINC; grep fraction_done client_state.xml
You may put this in a loop for watching it continously:
您也可以把它放在循环中,连续地观察它。
cd BOINC ; sh -c 'while grep fraction_done client_state.xml ; do sleep 10 ; done
The value shown is the fraction of the work done, so a value of 0.34 means 34% done.
显示的数字是工作完成的部分,所以0.34意味着已经完成了34%的工作。
#########################################################################
What does "exited with zero status but no finished file" mean? Is this serious?
-------------------------------------------------------------------------
The "exited with zero status but no 'finished' file" is a known bug in BOINC that we still couldn't track down. It tends to show up on Multi-CPU (or HT) systems, and if you look into stderr.txt in the slots directory you will probably find a message saying "no heartbeat from core client". However the Result is properly restarted by the client and will eventually finish, this bug hasn't an effect on the outcome. As long as everything else is working well, you can safely ignore this error message.
这个错误是BOINC中一个已知但我们无法跟踪的错误。它经常在一个多CPU或者多线程的系统中出现。如果您打开在slots目录的stderr.txt文件的时候,您会看到"no heartbeat from core client"。但是,客户端会正确地重新开始继续完成工作,不会对结果有影响。只要所有东西都正常,您可以忽略这个错误信息。
[BM]
#################################################################################
The benchmarks of my machine compared to machine XXX / OS YYY look way apart. Why is this?
---------------------------------------------------------------------------------------
When the BOINC client is first run on a machine, it does some testing to determine how fast that machine does floating point and integer mathematical operations. Some versions of the BOINC client do not make this determination very accurately, either over- or under-reporting the performance of the machine. In particular, on Windows machines, the MS compilers optimized away some of the benchmark tests, making the machines appear faster than they were. The opposite effect also arises on Macs and some 64-bit Linux machines, where the BOINC client would show better performance if it were compiled with additional optimization switches.
当BOINC客户端第一次在一台机器上运行时,它会进行一些测试以检验您的机器的浮点以及整点运算能力。BOINC客户端一些版本的测试并不十分精确,要么算多了,要么算少了。特别在使用Windows的机器上,微软的编译器会优化代码,使机器看起来比实际的表现要好。在苹果机和一些64位Linux机器上会有相反的效应,如果进行一些优化设置,BOINC的客户端会有更好的表现。
[BA]
##############################################################################
The downloads of the Workunits are quite large / too large for modem users.
------------------------------------------------------------------------------
The Einstein@Home workunits require a large data file (slightly more than 12 MB in size). With a 57.6kb modem, this file will take close to an hour to download. Once you have downloaded it, the Einstein@Home scheduler should send you a number of workunits for that file, so you won't need to download another file for some time. However be warned that sometimes the OUTPUT files from Einstein@Home can be quite large, and so it may take an hour or more to upload the results back to the Einstein@Home server.
Einstein@Home的工作单元需要一个大的数据文件(稍大于12MB)。以一个57.6kb的调制解调器连接网络来下载这个文件需要近一个小时。当您下载它以后,调度程序会给你发送几个工作包,所以你在一段时间内不需要再下载另一个文件。但是警告您,Einstein@Home的输出文件也有可能很大,所以您可能需要用一个小时或以上来发送这个结果。
The bottom line is that if you need to pay an hourly rate for dial up modem service, Einstein@Home is probably not a good thing to run on your computer. Users with broadband internet connections such as DSL (Digital Subscriber Line) and cable modems shouldn't find that these uploads/downloads take more than a minute or so.
底线是,如果您用的是拨号上网的话,Einstein@Home可能不是一个好的选择。用宽带上网的用户下载时间不应超过一分钟。
[BA]
############################################################
When showing the graphics the computaion slows down.
-----------------------------------------------------------------
Einstein@Home makes heavy use of OpenGL. The part of this work the graphics card can't do on its own hardware has to be done in software by the CPU, preventing it from crunching. If you have a slow or "dumb" (not OpenGL-accelerated) graphics card, you might better not show the graphics if you want to get your results finished quickly.
Einstein@Home用了大量的OpenGL技术。如果显卡的硬件不能自己完成这项工作,会有CPU通过软件完成,这就阻碍了计算。如果您有一款在OpenGL方面不那么“灵光”的显卡,为了使您的工作尽快完成,建议您关掉图像显示功能。
Here are a couple of ways to tell if Einstein@Home is being slowed down by your graphics hardware.
下面是检验Einstein@Home是否被显卡硬件拖慢的方法:
Windows users: soon after an Einstein@Home workunit has started, bring up the 'task manager' by doing CONTROL-ALT-DELETE. Find the running einstein process and compare how much CPU time is shown with the time reported by the BOINC client. The BOINC client only reports the CPU time that was used by the 'science' part of the code, whereas the 'task manager' shows the CPU time used by both the science code and the screensaver code. If you watch there for thirty seconds, and the BOINC client reports that the science code has done only an additional five seconds of computation, whereas the task manager reports that the einstein application has used an additional thirty seconds of CPU time, this means that the graphics is consuming most of the CPU time. In this case, you should probably set your screensaver preferences to blank the screensaver after a few minutes. Alternatively, go to the web site of your computer or graphics card manufacturer, and download the latest graphics drivers. If you can switch your graphics to a mode that supports 'accelerated 3D OpenGL' then the screensaver should become very efficient.
Windows用户:当Einstein@Home的工作包刚开始时,同时按下Ctrl+Alt+Del调出任务管理器。找出正在运行的Einstein@Home进程,与BOINC客户端中的时间比较。由于BOINC客户端只计算程序用于科学计算的时间,而任务管理器同时计算科学计算时间与屏保计算时间。如果您观察30秒,而BOINC客户端的统计只增加了5秒,任务管理器报告CPU时间增加30秒的话,表明图像显示占用的绝大部分的计算时间。这样的话,您应该设置您的屏保在几分钟后显示黑屏。另一种方法是登录您的显卡厂商的网站,下载最新的驱动。如果您能够将您的显卡设置为支持3D OpenGL加速的话,屏保会更有效地工作。
Linux users: It's important to make sure that your graphics hardware is using 3D OpenGL hardware acceleration. A good test is to run the 'glxinfo' program. If it reports direct rendering: No then you are NOT using graphics acceleration, and the graphics will be slow and time-consuming. If it reports direct rendering: Yes, then all is well. In many cases, where direct rendering is *not* enabled, you can turn it on. See http://dri.freedesktop.org/wiki/ for more information and a useful troubleshooting section. Running glxgears is a simple way to test changes to your XF86Config file.
Linux用户:确保您的显卡正在使用3D OpenGL硬件加速是很重要的。我们可以运行glxinfo程序来做一个很好的测试。如果它报告No,那么您没有开启3D OpenGL加速,图形的显示会变得很慢,而且极其消耗时间。如果它报告Yes,那么一切都好。在许多情况下,如果图形渲染没有开启,您可以开启它。运行glxgears是一条检查您的XF86Config文件的简单的途径。
Mac users: all recent versions of Mac OSX include wonderful hardware acceleration. You don't need to do anything!
苹果机用户:所有近来的Mac OSX版本都包含极佳的硬件加速。您什么也不用做!
[BA]
#######################################################
I'm afraid that the still parts of the graphics burn into my screen. Can I do anything? Will this change?
-------------------------------------------------------
Most modern computer screens are immune to burn-in, but we are still addressing this issue for those who are concerned. At some point in the future you will be able to select an item in your project-specific preferences (here) to ask that static elements of the screensaver not be shown.
绝大多数现代计算机的屏幕是不会被烧坏的,但是我们还是为了那些对此事关注的人将这个问题编入。在将来你可以(在这里)选择在屏保中不显示静态图像。
[EM]
#########################################################
The E@H deadlines seem too short for my computer.
---------------------------------------------------------
We have a deadline of one week between the time that your computer downloads some work, and the time that the results must be reported back to the server. In general, the Einstein@Home scheduler will try hard to NOT give your machine more work than it can do by the deadline. Normally these workunits take between 5 and 24 hours to do, so as long as your machine is available for Einstein@Home more than 15% of the time, it should be able to complete work on schedule.
我们有一个为期一周的最后期限,从您的电脑下载工作时算起。您的电脑应该在在最后期限之前完成并返回工作。总的来说,调度程序会试图不分发多于您的电脑能在最后期限前完成的工作。通常这些工作单元需要5到24小时来完成,所以只要您的机器在多于15%的时间为Einstein@home工作的话,这个任务是可以按时完成的。
We have received requests to increase these deadlines and may do so in the future. For the moment these are short for two reasons. First, if we increase the deadlines, this means that the work and result databases get bigger, because there is more work in progress. Currently, the database is the most overloaded part of the Einstein@Home server, and the part that does not scale well. So we are trying to keep it 'lean and mean'. Second, increasing the deadlines means that it will take longer for users to get credit. Since credits are the easiest way to keep track of whether or not your computer is working well and making a positive contribution to our research work, we would like to try and ensure that you get credits awarded in a timely way.
我们收到过延长最后期限的请求,并且我们将来也计划这样做。现在最后期限短有两个原因。首先,如果我们延长最后期限,由于更多的工作在进行,工作和结果数据库就会变得更大。现在,数据库是我们服务器最沉重的负担,根本不合比例。所以我们试图保持它的“整洁”。其次,延长最后期限意味着用户获得积分的等待时间会更漫长。由于积分是追踪机器是否正在工作的最佳途径,并且它也给我们的研究工作带来好处,我们努力保证您在较短时间内获得积分。
If you are having trouble completing work by the deadline, the simplest and best thing to do is to decrease the size of your 'work cache'. Go to "Your Account" and edit your general preferences so that 'Connect to network about every N days' is set to 0.1 days. This way, your computer won't download more work than it can do in a single day. Note that if you run multiple projects, you may need to set this value on the preferences page of your other project(s) too.
如果您对在最后期限之前完成工作有困难的话,最简单的解决方法就是减少您的“工作缓存”。在"Your Account"中编辑"general preferences",把"Connect to network about every N days"改为0.1天。这样的话,您的电脑不会下载超过它一天的工作量的工作。记住,如果您参加多个计划,您要在每个计划的设置页面上设置。
[BA]
[ Last edited by fwjmath on 2005-8-30 at 09:04 ] |
评分
-
查看全部评分
|