Can Einstein@Home pass the 1 Petaflop (1000 Teraflop) barrier? |
Message boards : News : Can Einstein@Home pass the 1 Petaflop (1000 Teraflop) barrier?
| Author | Message |
|---|---|
|
The computing power of Einstein@Home has exceeded 950 Teraflops for the first time since the project was begun in 2005. Based on the rate that our computing power has been growing, I am hopeful that Einstein@Home will pass the 1 Petaflop barrier before the end of 2012. Einstein@Home volunteers: please keep your computers running over the holiday season, and please sign up any new ones that you might receive as a gift! | |
| ID: 121230 | | |
|
This may be hard since SETI is back in action and shares GPU-s :( | |
| ID: 121232 | | |
|
We are working hard, in our challenge... | |
| ID: 121233 | | |
|
Everyone has a friend or family member somewhere that might be interested in volunteering their computing resources. | |
| ID: 121234 | | |
|
Os little team adds another 4MM credits to the E@H cause today... 1 PF mark is a little closer. | |
| ID: 121236 | | |
|
Adding a Radeon HD 7950 and two Radeon HD 6850s to help you reach that goal. | |
| ID: 121237 | | |
|
Sorry I can't keep my pc running over the holiday season. | |
| ID: 121241 | | |
|
Hello Bruce | |
| ID: 121242 | | |
We are working hard, in our challenge... Greetings and thank you! Bruce ____________ | |
| ID: 121243 | | |
Everyone has a friend or family member somewhere that might be interested in volunteering their computing resources. Thank you for your support, and remember, if it gets too hot in the bedroom, you can always open the window (:-). Bruce ____________ | |
| ID: 121244 | | |
Os little team adds another 4MM credits to the E@H cause today... 1 PF mark is a little closer. Thank you! Bruce ____________ | |
| ID: 121245 | | |
Adding a Radeon HD 7950 and two Radeon HD 6850s to help you reach that goal. That's the spirit!!! Bruce ____________ | |
| ID: 121246 | | |
Os little team adds another 4MM credits to the E@H cause today... 1 PF mark is a little closer. We will try to do our best and repeat/pass that mark today! If only i know how to make the 590/690´s use more than 50% of it´s real power... as is easy to do with his cousins 560/580/670/680... 5MM will be a easy task... SNIF!!! But still planning how to do that in the drawing board!!! Any help is helcome! (Yes, I allready increase the BRP factor...) ____________ ![]() | |
| ID: 121247 | | |
Hello Bruce Mark, thank you for the kind words, and for your support! Bruce ____________ | |
| ID: 121248 | | |
|
Do you have any idea Bruce what we will compute after finishing S6LV1 ? Are there any other project ideas beside the BRP4 Arecibo pulsar search? And maybe you or anyone else can answer one more question: Is seti@home still doing serious scentific analysis on their data like einstein@home does? | |
| ID: 121250 | | |
|
I have been to the LIGO Observatory in Hanford this summer (great tour btw!), and it looks like It is going to take a long time until we get new data. | |
| ID: 121251 | | |
Do you have any idea Bruce what we will compute after finishing S6LV1 ? Are there any other project ideas beside the BRP4 Arecibo pulsar search? And maybe you or anyone else can answer one more question: Is seti@home still doing serious scentific analysis on their data like einstein@home does? The Einstein@Home project is currently testing an extension of S6LV1 to higher frequencies. Hopefully coming soon to a computer near you! We'll continue with the BRP4 search indefinitely. First we need to catch up with the data backlog of about 13,000 beams (this will take a couple of months at the current rates) then we'll continue in the steady-state. PALFA is taking about 50 new beams of data per day, on the average, so this search will be running for some years, at least for as long as PALFA is collecting new data. I don't have any inside knowledge of the SETI@Home project, but have always thought that the basic idea is outstanding. This is high-risk/high-value research, in the sense that the odds of success are not high, but the payoff is huge. I personally am entirely sure that there is other life in our universe, but finding definite proof of this would be one of the most important discoveries ever for mankind. So personally I would be very happy to see SETI@home succeed in its goals. Happy Holidays, and thank you for supporting Einstein@Home! Bruce ____________ | |
| ID: 121252 | | |
|
I just added a cheap GPU to one of my less-capable crunchers. However, I set up new prefs for it to do GPU work only, and then I set it to no new tasks until it finishes all the CPU work it has on board. There is only one Einstein unit left, but a bunch of Seti. It should finish that up in a week or so and then I'll unleash the GPU for both projects. | |
| ID: 121253 | | |
|
Fingers Crossed that we can Achieve That Goal. My 2 Computers are almost Running 24/7. I just put them in Hibernate or Sleep Mode for a few hours or overnight, each couple of days, just to give them a rest. I only Shut Down about once or twice a week. I'm not expecting any New Ones at Xmas, but hopefully will be getting my Old Computer Working Again, and if I do, I'll be Activating it as soon as I can. I currently Run 5 Projects on My Desktop: Seti@Home, Einstein@Home, Cosmology@Home, Rosetta@Home, Milkyway@Home. I also have Orbit@Home, but have not done any work as yet, due to its Inactivity. On my Notebook (Laptop), I only Run Seti@Home due to it only having 2GB RAM and if I Run too many things on it, everything either Slows Down or Crashes. Even without any Programs Open, The RAM Usage is between 60 and 90 Percent. I do quite a few Einstein Tasks on my Desktop, and My Laptop is always loaded with Seti@Home tasks (I have had 35 Seti Tasks on it at one time). I actually got involved in The (Other) BOING Projects through The S.E.T.I. Program. | |
| ID: 121257 | | |
|
Today Ill add another 24/7 machine with Kepler GPU | |
| ID: 121259 | | |
|
Hi Bruce, | |
| ID: 121264 | | |
|
Suspended other causes to help achieve 1 petaflop goal. I should be getting a desk top soon. Will add as soon as I do. You people are doing great work and I wish others would join. I will also put it up on facebook. | |
| ID: 121277 | | |
|
Seti@Home has been giving fits over the past month ...and I know as an Einstein cruncher who had his project set for "no new tasks" while crunching SETI has returned full time after 3 years off and crunching high numbers. I`m sure other Seti crunchers just got fed up with the condiciton of the project and left, thus returning to Einstein@hoime like I did./...good luck and I hope yo umake it. | |
| ID: 121281 | | |
|
After fossicking about I've rustled up a couple of i7 machines with NVidia 560+ cards - they can do some fine E@H work when my kids aren't online gaming ( they have to sleep sometime ) - and I reckon I may find some more .... :-) :-) | |
| ID: 121282 | | |
I have found some great water cooling units that are sealed from Corsair ( H80i for ~ $140 AUD ) that drop the CPU cores down to ~ 25C. Big & quiet fans. Choice of brackets to mount to the various CPU form factors. Heat exchange right over the chip. No trouble whatsoever. Mike, those fans are listed as 120mm 2700 rpm. A pair that size running that fast would not be welcome companions in my study. What rpm do you find yourself actually running? And how do you find the fan noise? ____________ | |
| ID: 121285 | | |
I have found some great water cooling units that are sealed from Corsair ( H80i for ~ $140 AUD ) that drop the CPU cores down to ~ 25C. Big & quiet fans. Choice of brackets to mount to the various CPU form factors. Heat exchange right over the chip. No trouble whatsoever. Ah well, the part of the unit that sits on the CPU has a large push button on it ( or later models have an on-screen widget via USB if you like ) to cycle/select different behaviours for the entire assembly. From 'gentle' to 'aggressive' response, determining the fan speeds and the coolant pump rate. So the 2700 rpm is the max for that. I set it to gentle and for me it occasionally revs up but not for long. [ One can reduce the activity of the case fans on account of having the CPU cooler active, so there's a dB gain there too. ] Cheers, Mike. ____________ "I have made this letter longer than usual, because I lack the time to make it short." - Blaise Pascal | |
| ID: 121291 | | |
|
Another 4MM (3,991,963) added to the E@H cause yesterday but the total flops still at 943.4 TFLOPS. Did we reach the actual total capacity? | |
| ID: 121307 | | |
|
bonsoir ____________ | |
| ID: 121316 | | |
|
And this means in english?.. | |
| ID: 121318 | | |
|
My french is not that good, but it means something like: I'll stop crunching for my other projects and will focus on Einstein. | |
| ID: 121320 | | |
The computing power of Einstein@Home has exceeded 950 Teraflops for the first time since the project was begun in 2005. And now that you pointed that out, the project immediately got scared and the TFLOP amount is in decline ever since. ;-) ____________ Jord -The BOINC FAQ Service - BOINC 7.0 FAQ I used to be an adventurer like you. Then I took an arrow in the knee... | |
| ID: 121324 | | |
|
Why should Einstein@Home pass the 1 Petaflop (1000 Teraflop) barrier this time? | |
| ID: 121328 | | |
|
Another >4MM day (4,210,026) our team dialy record, a 20.1 Tflop added to the E@H pot! | |
| ID: 121330 | | |
|
预祝爱因斯坦@home项目的计算能力突破一千万亿次大关。 | |
| ID: 121332 | | |
预祝爱因斯坦@home项目的计算能力突破一千万亿次大关。 Which via Google translate: "I wish the computing power of the Einstein @ home project exceeded $ 11 trillion mark." Thanks for that! :-) Cheers, Mike. ( edit ) Adjusting the translation in context : $ 11 trillion = 1 Petaflop :-) ____________ "I have made this letter longer than usual, because I lack the time to make it short." - Blaise Pascal | |
| ID: 121333 | | |
Why should Einstein@Home pass the 1 Petaflop (1000 Teraflop) barrier this time? Note quite. The current run will be extended to cover higher spin frequencies, and after that is done we are planning to have a new search, using different methods but not waiting for the detector upgrades. See this thread for updates: http://einstein.phys.uwm.edu/forum_thread.php?id=9730. Cheers HB ____________ ![]() ![]() | |
| ID: 121335 | | |
And now that you pointed that out, the project immediately got scared and the TFLOP amount is in decline ever since. ;-) And will decline more when December maximum power -team challenge is over. I believe that most of GPUUG's members will switch back to S@H | |
| ID: 121343 | | |
And now that you pointed that out, the project immediately got scared and the TFLOP amount is in decline ever since. ;-) There's also BOINC's "debt" system which will have an effect: while SETI@Home was not able to distribute new work, many hosts participating in both S@H and E@H have received more work (and later credits) from E@H than they usually would according to the chosen resource share. BOINC tries to correct this in the long term by throttling the work fetch from E@H until the "debt" is repaid. Fair enough. Cheers HB ____________ ![]() ![]() | |
| ID: 121355 | | |
|
Real men run 24/7/365, year in, year out. No holidays or vacations, just brief downtime for hardware upgrades. Time to brass-up and hit 1 Petaflop. Your PC can holiday when you're dead. | |
| ID: 121356 | | |
Real men run 24/7/365, year in, year out. No holidays or vacations, just brief downtime for hardware upgrades. Time to brass-up and hit 1 Petaflop. Your PC can holiday when you're dead. I understand you're about to offer to pay my electricity bill for me? LOL ____________ | |
| ID: 121359 | | |
Real men run 24/7/365, year in, year out. No holidays or vacations, just brief downtime for hardware upgrades. Time to brass-up and hit 1 Petaflop. Your PC can holiday when you're dead. Depending on where you live, your computer might provide a cheaper heat source than your furnace. :) | |
| ID: 121364 | | |
|
Congratulations on almost reaching 1 Petaflop! | |
| ID: 121373 | | |
Congratulations on almost reaching 1 Petaflop! That made me wonder how compressible the data is, so I tried bzip2 compression on a couple of files:- p2030.20120101.G177.93-02.24.N.b1s0g0.00000_543.bin4 2098320 bytes in=> 450585 out h1_0403.95_S6GC1 8445248 bytes in => 7130498 bytes out So based on this limited sample, it appears BRP4 files are pretty compressible (almost 5x) but SL6V1 less so (<1.2x). If it's possible to somehow arrange compressed downloads for you, you could get almost 5 times the work in the same bandwidth. Is it possible to proxy e@h downloads? I think it downloads with wget or curl, so in principle it seems possible to insert a compress/decompress step. edit: compressing about 20 BRP4 files gave an average compression of ~3.58x; files fell into 3 roughly similiar sized groups, with compression rations of 4.72x, 3.73x and 2.84x) | |
| ID: 121374 | | |
|
Merry Christmas Bruce. I will leave my computer on for the rest of the year. Thank you for your commitment to the advancement of the understanding of nature. | |
| ID: 121385 | | |
I think that would be fantastic if there was a way to compress the data down in BOINC either with Bzip2 or possibly LZMA2 (xz). The compression ratios that you are seeing with BRP4 files are excellent. The bandwidth is the main item that has kept me from bringing more resources to the project. The previous reduction from 32 MB to 16 MB per task made by the project team was very helpful. However, even at 16 MB per task, I am looking at almost 19 GB of data transfer per day to bring all my resources online full time. | |
| ID: 121387 | | |
I think that would be fantastic if there was a way to compress the data down in BOINC either with Bzip2 or possibly LZMA2 (xz). From FileCompression: The BOINC client can handle compressed downloads using both the mod_gzip and mod_default mechanisms provided by Apache. However, resumption of interrupted downloads doesn't work with either of these methods, so we don't recommend using them. For application version files, you can specify a <gzip/> flag. This will cause the file to be transferred in compressed form to 7.0+ clients. and If you include the <gzip_when_done> tag in an output file description, the file will be gzip-compressed after it has been generated. The gzip_when_done is only supported in client version 5.8+. (ClimatePrediction uses this form) ____________ Jord -The BOINC FAQ Service - BOINC 7.0 FAQ I used to be an adventurer like you. Then I took an arrow in the knee... | |
| ID: 121389 | | |
I think that would be fantastic if there was a way to compress the data down in BOINC either with Bzip2 or possibly LZMA2 (xz). Thanks for the information. I wonder if it would be possible to have the BRP4 application itself link to one of the different available compression libraries and have the application handle decompression of the data files before starting processing of the data. | |
| ID: 121410 | | |
|
Thank you for looking into this. I did some compression experiments with the LIGO data (currently used in S6LV1), but not with the BRP data (at least not since ABP days). I wonder if it would be possible to have the BRP4 application itself link to one of the different available compression libraries and have the application handle decompression of the data files before starting processing of the data. This is what I'm planning to do: Link the application with zlib, so it can easily handle both gzipped and plain data, then add gzip as the last step of pre-processing. Shouldn't require much of a change. We are already using the gzip feature of the BOINC Client for result files in BRP and GW work (<gzip_when_done>), in fact this is why Einstein@Home requires a minimum Client version of 5.8. But I wouldn't rely on that feature for input/workunit files. BM | |
| ID: 121411 | | |
I did some testing last night and compressed a few of the .bin4 files with gzip. The files compressed from 2052K to 464-468K. This is a substantial reduction in file size. I think that linking the application to zlib would be very helpful. Thank you. | |
| ID: 121428 | | |
We'll continue with the BRP4 search indefinitely. First we need to catch up with the data backlog of about 13,000 beams (this will take a couple of months at the current rates) then we'll continue in the steady-state. PALFA is taking about 50 new beams of data per day, on the average, so this search will be running for some years, at least for as long as PALFA is collecting new data. Since we are processing an average of 166beams/day, does that mean that we are going to have a shortage of BRP4 tasks to feed all the GPU´s? ____________ | |
| ID: 121433 | | |
|
I figure my home computing taps me for 50 cents per day maximum. I'll balance my cost by having a glass of water rather than a can of diet coke. | |
| ID: 121434 | | |
|
Okie Dokie Smokey. We are crunching in Oklahoma. | |
| ID: 121437 | | |
|
We done all GPU BRP4 Units already, it seems ^^ | |
| ID: 121443 | | |
|
Just fired up my I7 2600k and gtx 580.I want a pulsar by years end so 24/7 runing hehe. | |
| ID: 121487 | | |
|
Running 6 cores, one is gpu- Einstein 4 ever, happy days !!!! | |
| ID: 121539 | | |
|
I don't think we'll reach it before the end of 2012. the FLOPS have been decreasing since days now. I guess most if not all SETI people have gone to their home and that's why we're seeing such decrease. | |
| ID: 121541 | | |
I don't think we'll reach it before the end of 2012. the FLOPS have been decreasing since days now. I guess most if not all SETI people have gone to their home and that's why we're seeing such decrease. Yep.. it doesn't look like: ![]() | |
| ID: 121543 | | |
|
Just fired up my I7 and nvidia gpu | |
| ID: 121545 | | |
|
I finally activated the new GT630 in one of my older crunchers. It immediately downloaded 16 Setis and 10 Einsteins, and got to work on the Einsteins in HP. | |
| ID: 121568 | | |
|
I got another one of my machines up and running. It is a 2 core AMD with no extra video processing power. I think if I put more RAM in it, it will be able to run a GPU. | |
| ID: 121572 | | |
I got another one of my machines up and running. It is a 2 core AMD with no extra video processing power. I think if I put more RAM in it, it will be able to run a GPU. System RAM shouldn't matter to the GPU. The GPU has its own RAM (unless it's a laptop). My new GT630 is crunching merrily away. Einstein units are getting downloaded in large quantities and processed immediately at HP, giving it little time to do Seti. (I suppose it could be working off debt from when it had a bunch of Seti to do on CPU and I wouldn't let it download any more for either project.) ____________ | |
| ID: 121574 | | |
|
Adding a GTX570 1280 MB (FERMI) in my 8 Core Mac Pro running OSX 10.8.2 to help you ! | |
| ID: 121588 | | |
|
I just stop other(SETI) proyect to start getting Einstein data and what happend? I was getting 512 WU and it say that this a limit of a day. Ok, no problem, but the problem is that i get 500 WU for CPU, maybe few less and around 15 for GPU. So, what can my sistem, i7 and 2 gtx460 do about that? Oh, busy a cpu for about 10 days and i can take a GPU out of the sistem. Beehh. | |
| ID: 121607 | | |
|
Hi Bojan, | |
| ID: 121609 | | |
Hi Bojan, i know that, but in pass(when a seti was down, start of december) i have limited my project at 1gb of hdd, i always getting around 20 GPU work and about 10 CPU work and disk of limited for BOINC was full. It seems that project was knowing what my sistem was needet, but now? Im getting a 500 CPU work for 10 days and almost nothing for GPU (GPU on my sistem is much faster), it will finished all work less in a day..... sorry for my bad english, hoppe that you understand me what i will tell you. | |
| ID: 121611 | | |
I finally activated the new GT630 in one of my older crunchers. It immediately downloaded 16 Setis and 10 Einsteins, and got to work on the Einsteins in HP. Well, offsetting that, my i7 finally finished the big load of Einstein it downloaded when Seti was down. Now I think it's paying back debt to Seti. The net change in my Einstein production overall seems to be slightly negative. ____________ | |
| ID: 121612 | | |
No problem, as soon as your system requires new work for GPU you will get it. Your GPU will never run dry. My systems fetch new work usually when downloaded wu's are at about 95%; that's early enough. Don't forget to keep one cpu-core free to feed the gpu. ____________ | |
| ID: 121614 | | |
|
"Don't forget to keep one cpu-core free to feed the gpu." | |
| ID: 121615 | | |
"Don't forget to keep one cpu-core free to feed the gpu." I use the same i7 as you do. I've set the amount of processors to 75%. This system has 2 AMD GPU's running 4 wu's at the same time + 4 CPU wu's. Setting the processor usage to a higher value decreases the performance of the gpu-tasks dramatically. When I stop GPU-work this system runs 6 CPU wu's. Since you have one GPU and run 2 wu's on it you should have 2 GPU + 5 CPU wu's running. Since you have a nVidia GPU that uses less CPU, other settings might be better. It needs some experimenting with these numbers to find the optimum setting. The settings I use are good for a system for daily work to keep it responsible. You can check your CPU-Usage life with a fine sidebar gadget from addgadgets.com ____________ | |
| ID: 121619 | | |
|
How are we doing with the Petaflop challenge? I was able to get a dual-core machine running again that had fried a power supply. Hope we can make it. | |
| ID: 121644 | | |
|
Mark, | |
| ID: 121649 | | |
|
Yep, that was me. Thank you for your quick response. | |
| ID: 121651 | | |
|
| |
| ID: 121668 | | |
|
Hello, [Im getting a 500 CPU work for 10 days and almost nothing for GPU (GPU on my sistem is much faster), it will finished all work less in a day..... I presume your system is just very fast and the boinc client got a bit overly excited about it when asking about all those tasks. To keep your GPU fed with data in a nice way, it is common practice to reduce the max CPU load to (n-1)/n*100% with the n the number of cores, so you have one free hand to feed the GPU all the time. I never understood why SETI has not long started to seek some help with external bandwidth, i.e. to get out of Berkeley at least with part of their infrastructure. It costs them dearly. Anyway, the Einstein servers just work, completely painless, at least from Europe. So, as long as your GPU is not idling, just relax about being swamped with too many work units. You may want to reduce the gigabytes available to BOINC if the situation does not improve. I am confident that the BOINC client gives priority to the GPU to have always units available. Together with the responsible E@H servers, this should hence be fine, even when disproportionate. If you run out of jobs for the GPU, but say they come back when you suspend running workunits, then this is a (new) bug. Steffen | |
| ID: 121669 | | |
I just stop other(SETI) proyect to start getting Einstein data and what happend? I was getting 512 WU and it say that this a limit of a day. Ok, no problem, but the problem is that i get 500 WU for CPU, maybe few less and around 15 for GPU. Hi Bojan, I have read all your messages and the replies. People have given reasonable answers but I think I can add more information to help explain what you are seeing here at Einstein. You mentioned (later message) that you have a 1GB disk limit for BOINC. When you first started to ask for work here, you were probably under that limit by a reasonable margin. The very first CPU task you received would have required a considerable download of both the apps themselves and a series of large data files (unless you already had them on board). If it was a GW task (S6LV1), the download could easily have been greater than 100MB. If it was a FGRP2 task, the initial download would have been more modest. However you still take a big hit in disk space as soon as the first GW task arrives. In both cases, once you have taken that hit, you can get many extra tasks that use the same data so your ongoing requirement for extra space is minimal until those large data files are 'used up'. For GW tasks, this can be hundreds or even thousands of extra tasks. For BRP4 tasks, the situation is quite different. For every single task you need 16MB of disk space. If you want to keep just 10 tasks in your cache, you need 160MB of disk space. On the other hand, if you wanted to have an extra 10 GW tasks, you may not even need a single extra MB. Extra GW tasks are simply extra sets of parameters to be applied to the existing large data files. These parameter sets are quite small and are stored within the state file (client_state.xml). They leave no additional footprint on your disk at the time of download. It's likely that the first request for work used up most of your available disk space. Once the limit was reached, you would not get more BRP4 tasks. However, the scheduler could choose extra CPU tasks that could use your existing data files and because you had a large cache setting, it would do so at every opportunity. The only way to get an extra BRP4 task would be to finish and report an existing one and free up 16MB of space. The scheduler could then send you one additional task - effectively just a replacement. So, what can my sistem, i7 and 2 gtx460 do about that? Oh, busy a cpu for about 10 days and i can take a GPU out of the sistem. Beehh. Assuming that you would simply like to see more GPU tasks in the cache, here's what I would do. Temporarily set your large cache setting to something much smaller so as to prevent any further CPU tasks (if you have plenty). You can change this locally or on the website, but if the latter, you need to 'update' your client so that it knows not to ask for more CPU work. If you change your prefs locally, the client will already know about it. You would then decide on how many extra GPU tasks you wanted to have. Let's say you wanted an extra 20 tasks. That translates into 320MB of space to store them. You would need to change your 1GB disk limit to 1.32GB. Again 'update' if necessary, to make sure the client knows about it. If your (temporarily reduced) cache setting is still large enough to allow it, the client should immediately ask for GPU work only and the server should send about 20 in total, perhaps over a couple of request cycles. Have a think about the above and please ask questions if anything is not clear. ____________ Cheers, Gary. | |
| ID: 121671 | | |
... in pass(when a seti was down, start of december) i have limited my project at 1gb of hdd, i always getting around 20 GPU work and about 10 CPU work and disk of limited for BOINC was full. It seems that project was knowing what my sistem was needet .... That was probably just good luck :-). When you first started, you probably only had a single frequency range for the large data files. As we are nearing the end of the S6LV1 run, it becomes increasingly likely that the scheduler will want to send 'left over' tasks for other frequency bins and this would require more large data files. Your ability to store GPU tasks is probably being swamped by the scheduler needing to give you more large data files. If you want to continue getting more GPU tasks you will probably need to allocate a bit more disk space from time to time. When the new run starts in January, it should be easier to manage your requirements. ... but now? Im getting a 500 CPU work for 10 days and almost nothing for GPU (GPU on my sistem is much faster), it will finished all work less in a day..... Your English is fine :-). Just use the 'trick' I outlined in my previous message. ____________ Cheers, Gary. | |
| ID: 121672 | | |
What is for you one Core on i7 which Intel say that have 8 Core? With modern CPUs you seem to always get a benefit by setting the BIOS to enable HT. So you will probably get the best outcome if you use the 8 virtual cores. If you were supporting one GPU, you would probably find that the best outcome would come from running 7 CPU tasks. With 2 GPUs, the best will probably come from running just 6 CPU tasks. As with most things, you need to try out various settings and see what works best for you. Another factor to consider is the number of simultaneous tasks you will run on each GPU. You may get the best performance from running 6 CPU tasks and 2x on each GPU which would give 10 simultaneous tasks. You could also try running 5/4 to see if releasing a further virtual core gave sufficient improvement to outweigh the loss of a CPU task - I suspect not, but that's just a guess. Im running 6 WU, 2 are free "HT" or i shuld run only 3 WU and realise 1 real core not HT one? I think virtual cores are good enough for GPU support. It would be a real waste to only run 3 CPU tasks :-). ____________ Cheers, Gary. | |
| ID: 121673 | | |
|
Hallo! | |
| ID: 121675 | | |
|
Thanks Gary Roberts and others for yours all replies. I just stop geting CPU work at beginning and now is fine. Still have around 300 CPU work to finish it utill 9.1.2013 and i hoppe that will manage all of them to that date. | |
| ID: 121677 | | |
|
Greetings! Just added a new notebook w/NVidia to the cause. 24/7 - but, only connects when I'm stopped for the night. | |
| ID: 121678 | | |
|
Is the rising computing power since the last few days (about 940 TFLOPS at the moment) real or just due to the very large credits per FLOPS ratio of the new FGRP2 tasks? Is this taken into account in the calculation? | |
| ID: 121680 | | |
|
Hallo Vegard! .... due to the very large credits per FLOPS ratio of the new FGRP2 tasks? Is this taken into account in the calculation? I believe it´s not taken into account. It results most likely from the verry high spread in crunching time, which is difficult to simulate in test runs. See here. For me this gives about 2.5 fold more credit/hour. For purpose of testing, this is ok. Kind regards and happy crunching Martin ____________ | |
| ID: 121682 | | |
|
Hi Martin, | |
| ID: 121684 | | |
|
Where are we at as of today? | |
| ID: 121686 | | |
|
Go to http://einstein.phys.uwm.edu/server_status.html and scroll all the way down to "Computing capacity". | |
| ID: 121688 | | |
|
The link points to | |
| ID: 121695 | | |
|
Oh, I overlooked this line of text, sorry... But I disagree that the answer is YES. I rather think that it depends on the conversion factors that are applied, if the numbers make sense or not. Would be nice, if an uncertainty could be calculated and written next to he numbers. Otherwise it will not be clear, if in the future we really passed any nice barrier like 1 PFLOPS or so... (And there are still the large discrepancies in the various webpages.) I am just surprised that we are celebrating the 950 TFLOPS (the first post by Bruce), while it is far from obvious (at least for the users) that this is correct. | |
| ID: 121697 | | |
... I am just surprised that we are celebrating the 950 TFLOPS (the first post by Bruce), while it is far from obvious (at least for the users) that this is correct. The thing that is being celebrated is really the rate of increase in the processing power of E@H. Not too long ago it was only half the current number. We have to measure it with some metric and as long as we keep using the same system and can be confident that the numbers are increasing, we can celebrate that fact and can mark out some milestones to celebrate as we pass them. I'm just a volunteer like everyone else outside the actual project staff. I think the staff do a great job of maintaining a reliable and responsive system and this encourages increased participation. Strangely enough so does setting some sort of target to aim for. I've been pleasantly surprised at the number of messages that have popped up recently in various threads from average volunteers committing to help reach the target by switching resources here, or adding new resources, or dragging old hardware out of retirement, etc. When Seti came back on line, I was expecting progress to drop backwards sharply. What I wasn't expecting was the quick recovery that has now occurred. Sure, a significant proportion of this upward spurt is due to the fact that tasks in the new FGRP2 run are crunching rather quickly. But I'm sure there is also the help of both existing and new volunteers who are adding resources in response to Bruce's messages. In my own case, in the last couple of months I've added 15 new budget GPU crunchers. I didn't do that in response to any 'call to arms' but it turns out the timing was pretty good to help Bruce's current call :-). My reasoning was quite different. I had discovered the very good power efficiency of Kepler series GPUs and when the GTX650 came out at a nice cheap price, I couldn't resist. The original plan was to shut down a swag of high consuming 3 year old CPU only crunchers and pay for the upgrade with electricity savings whilst actually increasing my RAC. The plan would have worked admirably. The new GPU crunchers have a combined RAC of around 400K. The original CPU fleet was producing 250K. When it came time to start shutting a lot of them down, Bruce had started his comments in these news threads so I didn't have the heart to withdraw them. Now that FGRP2 has arrived, my RAC has shot up even further. I've suddenly got a goal of my own - to reach 1M RAC by the end of the year. A week ago I didn't imagine it would be possible. But with three hours to go here in Brisbane, Queensland, my RAC is now over 997K and rising at a rate that should get me there. I imagine Bruce is very pleased with his cunning psychology to lure people in and boost the contributions to the cause :-). ____________ Cheers, Gary. | |
| ID: 121698 | | |
|
Gary, | |
| ID: 121699 | | |
|
Hallo Vegard! I rather think that it depends on the conversion factors that are applied, if the numbers make sense or not. As long as I´m with this project, this is more than 7 years now, the conversionfactor is stable at 1,02*10^-5 (TFLOPS/(Cobblestone/d)]. - for E@H !!! - This I prooved by taking the daily data from the server status page, put them into a graphic and made a least square fit. The correlationfactor R^2 for this is 0,99991, so verry good. But intentionaly the factor is 1e-5 --- 100,000 Cobblestone/d for 1 TFLOPS. I think, the difference is somewhat difficult to rule out here. The definition of the Cobblestone for the done crunching work, was set up for a better comparison of the different BOINC-projects. By the way, we will get a new peak crunching power this afternoon. The old maximum was 953,8 @ Dec. 10th 20:35.Now it´s 952,5. Best whishes for a happy, healthy and wealthy NEW YEAR 2013 !!!! Kind regards and happy crunching Martin ____________ | |
| ID: 121700 | | |
|
Hi Martin, | |
| ID: 121701 | | |
The old maximum was 953,8 @ Dec. 10th 20:35.Now it´s 952,5. New Einstein Max: 954.2 TFLOPS! . . . let's keep pushing! | |
| ID: 121702 | | |
|
I was right. No 1 PFLOPS at the end of 2012. Let's hope we can reach it shortly into 2013 | |
| ID: 121703 | | |
|
Hi Vegard! ... Flops estimation and Credit will be fine-tuned when we have more data (i.e. tasks returned), but possibly not this year anymore. Obviously the amount of data in the different tasks and so the amount of crunching work and crunching time, changes thoroughly from task to task. From my observations of 244 tasks now, I conclude, we have about a factor of 2.5 to much credits/task now, compared to S6LV1. Kind regards and happy crunching Martin ____________ | |
| ID: 121704 | | |
|
Hallo Sid! | |
| ID: 121705 | | |
|
| |
| ID: 121708 | | |
When Seti came back on line, I was expecting progress to drop backwards sharply. What I wasn't expecting was the quick recovery that has now occurred. Sure, a significant proportion of this upward spurt is due to the fact that tasks in the new FGRP2 run are crunching rather quickly. But I'm sure there is also the help of both existing and new volunteers who are adding resources in response to Bruce's messages. I tend to think the current upsurge is at least partially due to Seti's latest problem with downloads getting stuck again. That said, I just watched my i7 suddenly clear out a large backlog of Seti downloads in just a few minutes, at speeds approaching 60Kbps. However, the host with the new GT 630 still has a whole bunch that aren't going anywhere at any speed. ____________ | |
| ID: 121709 | | |
Edit: Bugger, I may have spoken too soon, you just dipped under again! Hi Gavin, thanks for your congratulations and good wishes. Yes, I did 'make it', I believe, but I didn't stay up to see it. The data bandwidth required to feed the GPUs is quite onerous. My ISP has a peak allowance and a very much larger off-peak allowance. I take advantage of this by restricting comms to the off-peak period (2.00am to noon local time). I don't pay for uploads so results are uploaded during peak time (noon to 2.00am) but (unless I'm very keen) are not reported. Last night I reported the backlog on the GPU hosts around 10:30pm and saw that there would be enough to push the RAC above 1M by midnight. When I got up this morning, the off-peak period was well underway and all hosts had requested work to replenish caches and had reported their completed backlogs. So I'm now well above 1M. When I look at daily increments in total credit, those are running at around 1.4M. So RAC will continue to rise until the credit allocation for FGRP2 is adjusted and/or I decide to complete my strategy of actually turning off the 'gas guzzlers' :-). I'll be leaving them on until we hit 1PF at least :-). It's amazing how much we get sucked in by rising numbers :-). ____________ Cheers, Gary. | |
| ID: 121710 | | |
... partially due to Seti's latest problem with downloads getting stuck again. I don't follow Seti so I'm quite oblivious to whether the project is running normally or not. I do understand that Seti supporters tend to keep large caches and tend to use E@H as a backup. Unless Seti has not been supplying work for a few days, I wouldn't think we would see much effect here yet. Sure, caches might be having the shortfall supplied by E@H but until Seti tasks actually run out, I wouldn't think that more E@H tasks are being crunched yet. ____________ Cheers, Gary. | |
| ID: 121711 | | |
... partially due to Seti's latest problem with downloads getting stuck again. I think there's a fair chance we should be able to declare the Petaflop within the next 36 hours. SETI has been limping for a while, with a recurrence of the scheduler timeout problem it suffered at the very beginning of November. And around 02:50 UTC this morning, one of their collection of creaky and cranky servers left the party: no work has been sent out or reported since then. They are also due for scheduled maintenance - probably tomorrow, after the holiday. That means we should get the benefit of the big post-holiday office switch on tomorrow, when their volunteers fetch from backup projects. And even if we miss this opportunity, Berkeley has another outage scheduled for electrical supply work between 4-6 January... 965.7 TFLOPS and rising. | |
| ID: 121713 | | |
|
Hi Richard, thanks very much for the update. Interesting days ahead!! Looks like we might need to get ready with the welcome mat once again!! :-). | |
| ID: 121716 | | |
|
Overclock.net have added E@H as one of their three "Projects of the month"... | |
| ID: 121717 | | |
965.7 TFLOPS and rising. 970.1 TFLOPS That calculated/reported figure has been rising at a very steady 1 Tflop/hour since I posted it. Still on course for 22:00 UTC tomorrow? | |
| ID: 121718 | | |
|
976.8 as of now :) | |
| ID: 121722 | | |
|
The only problem is that you don't seem to have enough work lined up. I am only a small contributor, with a little less than 700k work units done, but I frequently find that you don't have work for my i7 computer. | |
| ID: 121723 | | |
The only problem is that you don't seem to have enough work lined up. I am only a small contributor, with a little less than 700k work units done, but I frequently find that you don't have work for my i7 computer. See your Einstein@Home preferences, especially the row "Run only the selected applications", they must be set to "yes" (checked). And "If no work for selected applications is available, accept work from other applications?" must be checked. If you don't have GPU, you can "Run CPU versions of applications for which GPU versions are available" (check it, if it's not). ____________ | |
| ID: 121724 | | |
|
I agree, there must be something with the settings. | |
| ID: 121725 | | |
Hallo Vegard! Hi Martin, just to be shure that I understood this right: a RAC of 50.000 means 0.5 TFLOPS / day? Is there a definition for the 'Cobblestone'? ____________ | |
| ID: 121726 | | |
|
Hallo Alex! a RAC of 50.000 means 0.5 TFLOPS / day? Is there a definition for the 'Cobblestone'? The ratio would be 50.000 Cobblestone per day equals 0.5 TFLOPS (Terra Floatingpoint Operations per Seconde) That´s right. How these FLOPS have to be determined, I don´t know. I believe, one can find the definition somewhere in the literature describing, how to setup a BOINC project. By the way: We may hit the 1 PFLOPS tomorrow, but at midnight it´s back below this line. But on Thursday it will be well above this line, hopefully. Today we had an increase of 17,1 TFLOPS and we need another 25,2 TFLOPS only. A happy, healthy and wealthy year 2013 !!!! Kind regards an happy crunching Martin ____________ | |
| ID: 121730 | | |
|
yea seti is down again so I guess i'm back with a paltry 4.2 terraflop | |
| ID: 121732 | | |
|
For the record: 985.5 | |
| ID: 121738 | | |
|
I've made a challenge over at BOINCstats called "PetaFLOP Crunch" to celebrate the upcoming 1 PFLOP for Einstein@Home. I think we will reach the 1 PFLOP before the challenge's start (which is 5th jan 2013) but it doesn't matter... Anyone is welcome to participate in the challenge and late entrants are allowed as well. | |
| ID: 121740 | | |
|
Hallo! | |
| ID: 121741 | | |
Hi Martin, FLOPS calculations are from credits (which should be proportional to the number of calculations in the job) from all users/hosts. So for now project FLOPS estimate a slightly overrated due high credit value of FGRP2 WUs. Reason for huge (usual x2) differences of FLOPS numbers on different BOINC webpages is usung different formulas to convert credits/day to FLOPS, which is a lot of confusion with it. More on this, I wrote in this thread on Rosetta@Home forum: http://boinc.bakerlab.org/rosetta/forum_thread.php?id=6156&nowrap=true#74675 (from this post and to end of thread) P.S. New E@H record - 990.9 TFLOPS | |
| ID: 121742 | | |
... partially due to Seti's latest problem with downloads getting stuck again. It turned out the download problems I was having were on my end (I had a hosts file specifying all Seti downloads to come from one server; I removed the entry and the backlog cleared in minutes). However, I haven't checked there in a couple of days; it sounds like you're saying there is a new problem I haven't heard of yet. Oh joy. David ____________ | |
| ID: 121746 | | |
|
FTR: 994.5 | |
| ID: 121749 | | |
|
996.6 TF !! :-) | |
| ID: 121755 | | |
996.6 TF !! :-) Yes, that was the mark at 22:30 - so I lose the bet I made with myself: I think there's a fair chance we should be able to declare the Petaflop within the next 36 hours. But we're still climbing (996.9 as I type), and SETI are still struggling, so I'm sure y'all will have cracked it by the time I wake up tomorrow morning. | |
| ID: 121756 | | |
FTR: 994.5 Now down to 993.6. | |
| ID: 121758 | | |
|
Yep, but rising again. There were some network problems @UWM which caused some interruption in the daemons' (e.g validators) work, roughly from 21:00 to 21:30 UTC. Needed some manual intervention to get some going again, but all should be working now. Just a little delay... | |
| ID: 121759 | | |
|
Hallo! | |
| ID: 121763 | | |
|
just a thought I am running about 4 tflops | |
| ID: 121764 | | |
|
Oh yeah - 997.7 :-) | |
| ID: 121765 | | |
|
I just reported 202 completed tasks from 7 hosts with GPUs. | |
| ID: 121767 | | |
|
999.2 TFLOPS :) | |
| ID: 121768 | | |
|
999.6! Could be the next update's the one. | |
| ID: 121769 | | |
|
Congrats get your beers and ciggars ready! | |
| ID: 121770 | | |
|
Way to go E@H contributors, massive epic effort !! :-) :-) | |
| ID: 121771 | | |
|
congratulations to all of us for hitting the petaflop. | |
| ID: 121772 | | |
|
Congrats us :D | |
| ID: 121773 | | |
|
Good stuff everyone, let's find some pulsars!! | |
| ID: 121774 | | |
|
| |
| ID: 121775 | | |
|
now can you do 100 petaflops. | |
| ID: 121776 | | |
|
yayyyyy we reached it! :D | |
| ID: 121777 | | |
|
I hate to put a damper on the celebrations but I don't think this is a real record. The RAC that is used to determine the 1 Petaflop barrier is currently inflated with the to high credit values for the FGRP2 results. | |
| ID: 121780 | | |
|
Sure, the whole thing is just numerology, but it's still fun. | |
| ID: 121782 | | |
|
Congrats all! | |
| ID: 121784 | | |
I hate to put a damper on the celebrations but I don't think this is a real record. The RAC that is used to determine the 1 Petaflop barrier is currently inflated with the to high credit values for the FGRP2 results. Lets just use FGRP2 as a baseline and increase the S6LV1 and BRP4 credits so we can break the 2 petaflop barrier ! :) | |
| ID: 121785 | | |
|
Good that I left my laptop turned on overnight so we made it! :) | |
| ID: 121788 | | |
I hate to put a damper on the celebrations but I don't think this is a real record. The RAC that is used to determine the 1 Petaflop barrier is currently inflated with the to high credit values for the FGRP2 results. There's always a party pooper... ____________ ![]() Team Belgium | |
| ID: 121789 | | |
I hate to put a damper on the celebrations but I don't think this is a real record. The RAC that is used to determine the 1 Petaflop barrier is currently inflated with the to high credit values for the FGRP2 results. The same think i here to. On SETI i get in 24/7 30.000/33.000 RAC a day but here i get wit easily RAC of more then 60,000/day. But we get a PTERALOP from a RAC, that somene explain it before how, not from a real CPU/GPU Power. So, any chanche that someone explain it how can we manage to reach a real Pteraflom without a "cheating" of that sort computation? Thanks and cheers | |
| ID: 121792 | | |
|
Hallo Henk! The RAC that is used to determine the 1 Petaflop barrier is currently inflated with the to high credit values for the FGRP2 results. I think, this is only correct in parts. You neglect the tremendous increase of crunching power of the BRP4 by a factor of 3 at minimum, within the last 4 month, as you can see here. I feel sure, that BM will correct the earnage of FGRP2 soon. It´s a difficult task, as the crunching times do vary by a factor of 10. I had crunching times at minimum of 0.44 h and maximum of 4.5 h, with a mean value of 2.89 +/- 0,68 h ( derived from 320 tasks). That is much wider than in former projects. Kind regards and happy crunching Martin ____________ | |
| ID: 121793 | | |
|
Hallo dancer42! now can you do 100 petaflops. Ok! If we can hold an daily increase of 1% in crunching power, we will reach this within 463 days, that is about 1,25 years. Today we will have an increase of about 1.5%. Sooo, what do we wait for ????? Best you start immediately. Kind regards and happy crunching Martin ____________ | |
| ID: 121794 | | |
|
It's a milestone thing. Something we can celebrate for it's own sake. In and of itself ..... :-) :-) | |
| ID: 121795 | | |
... Bruce Allen has compared E@H's power to that of a dumptruck ... So if E@H is a dumptruck, are we going to be 100 dumptrucks in 463 days time? :-). Anyone want to start a book on when we'll get to 2 dumptrucks? :-). ____________ Cheers, Gary. | |
| ID: 121796 | | |
... Bruce Allen has compared E@H's power to that of a dumptruck ... OK Gary, so be it! :-) 1 BYDT = 1 BigYellowDumpTruck = 1 Petaflop I'll go for 2 BYDT's no later than Northern Summer Solstice* !! :-) and then go for a fleet : ![]() Cheers, Mike. * June 21st 2013 at 05:04 UTC ____________ "I have made this letter longer than usual, because I lack the time to make it short." - Blaise Pascal | |
| ID: 121797 | | |
|
| |
| ID: 121798 | | |
|
Einstein@home ya supero el teraflop 1012,9Teraflops!!!!!!! | |
| ID: 121800 | | |
|
Hi! | |
| ID: 121802 | | |
I hate to put a damper on the celebrations but I don't think this is a real record. The RAC that is used to determine the 1 Petaflop barrier is currently inflated with the to high credit values for the FGRP2 results. IMO, the credit should represent more than raw FLOP count. The Fermi and Arecibo data has proven rather useful from a scientific POV, with numerous observational successes. That ought to count for something. | |
| ID: 121811 | | |
Somebody at slashdot was thinking we ought to be counting in base-2 rather than base-10, and gave us a new target of 1024 TFLOPS to aim for. Done. BM | |
| ID: 121812 | | |
|
I hope that my computer that running 24 Hours can help you. | |
| ID: 121814 | | |
|
It's at 1023.1. Congrats to all. | |
| ID: 121819 | | |
|
Congratulations to all! | |
| ID: 121825 | | |
|
At least for the time being, we seem to have reached a plateau at 1026.9 | |
| ID: 121837 | | |
|
FGRP2 TFLOPS decrease now (190) and overall TFLOPS still increase (1034), so I would say it is a true, honest record. | |
| ID: 121865 | | |
|
Congratulations on passing 1 PFLOPS! | |
| ID: 121866 | | |
|
found that on gulli.com (sorry, german) | |
| ID: 121867 | | |
At least for the time being, we seem to have reached a plateau at 1026.9 FTR: 1030.4 TFLOPS for almost 2h now. BM | |
| ID: 121874 | | |
|
i signed up for this project on the 24th and haven't stopped working on it. yay me i helped do something!!!!!! | |
| ID: 121877 | | |
|
Oh, no! ;) | |
| ID: 121926 | | |
|
I suspect the drop is more do to the BRP4 validators being off line until tomorrow. | |
| ID: 121927 | | |
I suspect the drop is more do to the BRP4 validators being off line until tomorrow. Indeed so. We're back above 1000 TFLOPS (1000.8, to be exact), and there are still 31,448 BRP4 tasks in the validation queue. | |
| ID: 121962 | | |
I suspect the drop is more do to the BRP4 validators being off line until tomorrow. There seems to be something quite peculiar going on. We are now back to 1022 and the BRP4 backlog is 9082 so a *lot* of BRP4 tasks have now been cleared. That's fine you say - the spurt is coming from the spurt of BRP4 validations. If that is true, then why has the BRP4 individual TFLOPS continued to go down. Its now 511 and I'm sure that it was about 550-560 (or even more) about a day ago. I'm only going on memory - I didn't copy anything down - but I've been watching the decline in the FGRP2 value as a result of the credit adjustment and have been expecting the total figure to really drop under the combined effect of both pulsar searches having (for the moment) significantly lower numbers. Someone can correct me if my memory is faulty, but just after new year when 1 PF was reached, we had the following very approximate figures.
| |
| ID: 121969 | | |
If that is true, then why has the BRP4 individual TFLOPS continued to go down. The "individual FLOPS" on the server status page are highly misleading, especially for applications that feature GPU versions. Shown there are really CPU flops based on CPU time of reported results and finally scaled such that the sum equals the total project FLOPS. So if the individual FLOPS of one application is declining, it could (and in this case probably does) just mean that we get more tasks (i.e. credit) from the GPUs of that search. BM | |
| ID: 121970 | | |
This is what I'm planning to do: Link the application with zlib, so it can easily handle both gzipped and plain data, then add gzip as the last step of pre-processing. Shouldn't require much of a change. This feature is currently being tested on the BRP4 applications over on Albert@Home (the current OpenCL app versions aren't working for different reasons). If you're interested in that feature, you my want to help us testing. BM | |
| ID: 121973 | | |
|
2 Gary Roberts | |
| ID: 122042 | | |
BTW seems S6LV1 and S6BucketLVE statistic is mixed up? I think S6LV1 is already finished and replaced by S6BucketLVE? S6BucketLVE has not started yet - take a look in the 'Workunit and Tasks' block - all the values are zero. In contrast, S6LV1 suddenly has over 200K tasks 'ready to send' and that is the clue as to what is going on. A project is listed as '100%' when there are no more tasks to generate and not when all tasks have actually been completed. It is common practice at E@H to generate and dump into the database all remaining tasks for GW runs when the run is getting quite close to completion. That has now happened. It will actually take quite a few days yet for the 200K remaining 'primary' tasks to be distributed and then it will take many weeks to months for all the 'secondary' and 'tertiary', etc, tasks (required because of failure of primary tasks) to be sent out and returned. It will be quite a long time before S6LV1 is 'finished'. The new run will be started shortly and this will tend to divert resources away from 'finishing' the previous run. This can create a problem for volunteers who have stringent monthly bandwidth caps. Some of that bandwidth will need to go to new large data files required for the new run. An increasing amount of bandwidth will be required for blocks of large data files (for the old run) that will need to be sent if a host is allocated a 'resend' task (for a failed primary task) for a frequency bin other than that for which it has the appropriate large data files already on board. When all 200K primary tasks are gone, the LV1 'diet' will be resends only (for however long it takes for the run to 'finish'. If bandwidth is not a problem, it would really be appreciated if hosts are left 'available' to accept resends. If bandwidth is a problem, check out your E@H preferences and you will find there are now separate listings for both GW runs. ____________ Cheers, Gary. | |
| ID: 122048 | | |
...it would really be appreciated if hosts are left 'available' to accept resends. As a relative newbie, does that mean doing something special? (or just not fiddling :) ). | |
| ID: 122049 | | |
...it would really be appreciated if hosts are left 'available' to accept resends. When we are at the end of one run and ramping up a new one, then there is a lot of tidying up to do with respect to 'loose ends' or work units not satisfactorily completed for the retiring run. These work units often come from rather different places in our search parameter space with the effect of sometimes requiring large downloads for users. This is because here at E@H we use 'locality scheduling' which has the marvellous benefit of examining what data a given host already has and, if possible, making good use of that circumstance by allocating work units relevant to that already held data. But if we jump around parameter space then that benefit is lost as new data sets relevant to disparate parameter choices need downloading. Some users prefer not to be involved in that scenario and thus come back to E@H later on, after such work units are dealt with and the new run is well on the go. Cheers, Mike. ____________ "I have made this letter longer than usual, because I lack the time to make it short." - Blaise Pascal | |
| ID: 122050 | | |
...it would really be appreciated if hosts are left 'available' to accept resends. It means, "Don't disable S6LV1 in your prefs just because you think it's finished" ;-). The nice thing about 'appropriate' defaults for new preferences is that most people will be unaware of the change. So most will end up doing the 'right' thing :-). Since I may have alerted people to a new pref setting they could play with, (this is a popular thread), I thought I'd better put in a 'plug' for the important job of cleaning up the resends - by not taking advantage of the new pref and bailing out. ____________ Cheers, Gary. | |
| ID: 122051 | | |
|
2 Gary Roberts | |
| ID: 122052 | | |
If it mark task as "done" after it pass from WU generator to DB it can explain "strange" statistic. This would be a bit clearer if the 'search progress' block had different headings which said, "Total Needed", "Already Generated" and "Still to Generate" or something like that. It still leaves the (pretty much unsolvable) problem of how best to indicate that there will be a large (but unknown) number of resends to be sent out later. You may not know a resend is needed until a 14 day deadline passes and this cycle can be repeated quite a few times. If people have all moved on to new and greener pastures, it will slow down the cleanup. In the end, to shorten the agony, the Devs may well send out extra copies of resends just to make sure at least one is returned in a timely fashion. Another possible choice is to do the final cleanup 'in-house'. But then how to explain this message poping up(all last day) in the logs of of my BOINC client? Well, the first one is a 'no-brainer' - there genuinely was no work to send. The second one needs a bit more explanation. I've seen this quite regularly on certain hosts over the last year or three :-). It doesn't happen on all my hosts but I use all available 'venues' and I do have a mixture of server-side prefs on most and local over-ride prefs on some and I haven't sat down systematically to diagnose exactly what is going on. I did mention it in a message a long time ago and Bernd did make an explanation which I don't think I understood at the time and which I've certainly long forgotten now anyway. I didn't pursue the matter at the time because the client was always able to (eventually) get what it wanted by being a bit persistent with the server. Maybe it would ask a few times for a certain type of work and be refused with a 'no work available' answer but then, after yet another request to the server, the request would suddenly be granted. I don't know for sure, but I think the explanation goes something like this. There are (I think) server-side settings that control what the scheduler 'prefers' to give you when you request work. To keep it simple, let's assume that for 40% of requests, the scheduler wants to send you FGRP work and for 60% of requests the scheduler wants to send GW work. If your prefs allow any type of CPU tasks or if you have said 'yes' to the pref setting about 'other apps' if work for your preferred app is not available, I think you will always get what the scheduler has chosen to send. If you have excluded one of the apps and said 'no' to 'other apps' I think you may very well get the 'no work available' message, even though there actually is work available. It's possible you may need to go through this cycle a few times until the scheduler's choice of what it prefers to send actually coincides with the search that your prefs allow and so you get the work. I have seen this sort of cycle so many times (with the ultimate happy ending) that I don't even worry about it anymore. The full explanation must be more complicated than this because it doesn't happen on every host that always asks for just one particular type of work. It seems to happen on hosts that have complicated preference settings, particularly when there are some local over-ride settings in play. I just haven't felt the urgency to attempt to document it better, particularly as the server code is rather old and will eventually be updated anyway. Server offer for me only BRP4 and FGRP2 Wus last days. When I try to opt-out of them in prefs then server respond by: Be persistent with extra work requests. The scheduler will eventually give you what you want. At least it does for me. ____________ Cheers, Gary. | |
| ID: 122055 | | |
... *Disclaimer: This could very well be totally wrong or outdated info. I have a faint memory of an explanation that the server is a bit reluctant to switch you over to a new full set of large data-files if that could be avoided, it waits for a host that already has the right files. The time the server is willing to wait is limited and that is why the request eventually succeeds, probably giving you a larger download. Or maybe some resends has been generated while you wait... ____________ | |
| ID: 122056 | | |
Message boards :
News :
Can Einstein@Home pass the 1 Petaflop (1000 Teraflop) barrier?