找回密码
 新注册用户
搜索
查看: 6831|回复: 2

[项目新闻] RieselSieve [已结束]

[复制链接]
发表于 2008-2-8 18:45:12 | 显示全部楼层 |阅读模式
从 2006-09-15 GMT 01:15 开始更新~  (更早的全部找不到了)
超过两个月的旧闻恕不翻译


2006-08-11 GMT 01:15    Client Version 5.26 Released

The 5.26 version of the Riesel Sieve BOINC client has been released - 5.25 was released very briefly, but it mistakenly didn't include one of the (last minute) changes we made. Features: -Fixes 5.24 bug of CPU time updating once every 60 seconds (counts correctly now) -Honors user preferences of disk write times - Note: this only applies to the wrapper itself, which is controlled by BOINC. The sieve client intermittently writes its factors found to disk - I can't control that from BOINC. -Fixes 5.24 bug of riesel-sieve_xxxxxx_x_log.out receiving a -161 (file not found) error -New version of the JJSieve Client, allowing us to have progress reports every 10%, as well as better startup/finish error handling (will be further implemented in the 5.27 version)


2006-08-16 GMT 02:49    High WU Error Rate 5:45-6:45 UTC

You may have noticed nearly every WU issued from 5:45-6:45 UTC (1:45-2:45 EDT) today was being errored out code -200 (invalid checksum or transfer error). The new WU's were finally reached, and a bug in creating them was found. There is another check in them to prevent problems with overwritten ranges, related to multi-cores, however I didn't make a corresponding change to file size inside the work generator. This caused all the WU's to error out. I have cleared them & reissued with the right file size. If you have some of these WU's, you may notice errors sending them back in (which is fine). Abort them if they refuse to go away. Issued after 6:45 UTC, these WU's should be fine (although I think they'll have new numbers. Everything was wu_60624 and up. Sorry about the problem, it is now fixed.


2006-08-27 GMT 01:11    Client Version 5.27 Released

The 5.27 version of the Riesel Sieve BOINC client has been released - this release is essentially 5.26 with a very minor change. Features: -Stderr.txt includes \r\n rather than \n, to better display the stderr output on web pages.


2006-08-29 GMT 01:11    BETA Status Announced

Coinciding with the release of the 5.27 Client, we are pleased to announce the move to Beta status for Riesel Sieve. We're pleased with the performance of the 5.26 client, so the minor change to reach 5.27 will mark our beta release. Thanks to all of our Alpha testers, welcome to those who join us as Beta testers!


2006-08-29 GMT 00:45    Errors from 04:00-05:00 UTC / 12AM-1AM EDT

Ignore all client errors from 12AM EDT - 1AM EDT today. It was all me - we tried to pull in some old ranges for cleanup and things went wrong. Mainly a download problem (not sure where), but then a massive, DDOS-style wave started as all the hosts tried to quickly grab work (which didn't work, since the same WU's were being sent out). Stopped those WU's from being sent out, but there could be resiudal errors for the next little bit. Sorry and thanks for your patience.


2006-09-03 GMT 15:16     Load Problems Noon- 3pm EDT (16:00-19:00 UTC)

We had another load spike this afternoon. Fortunately, I was around to try and take care of the problem while it was happening this time. I've implemented several changes to watch the load when and if a spike occurs again. If it does, things like work regeneration and result validation, which are very CPU-intensive, will be temporarily paused. While this will casue workunits to show up as pending in this situation, it will allow the project to continue running, as the load will be significantly lower. We're watching the situation, still working to find the original cause of the problem, and trying to prevent further issues. Thanks to everyone for their support and understanding.


2006-09-05 GMT 19:57    Database Issues Last 48 Hours

Over the last two days, there has been a huge increase in "Results in Progress", followed by a large drop this evening. This, and several other problems, have been due to the load & DB issues we've had over the last 2-3 days, which are now resolved. We tested a new Linux and BSD application, but when I removed the DB entries, any host on Linux or BSD attempted to grab work with no application to crunch with. These WU's were not reported back, which lead to a bigger and bigger (9,100+) queue of WU's that were doing nothing. They have all been invalidated, and Linux/BSD clients cannot get more work right now. Additionally, there is a large amount (probably close to 5000) of "phantom" workunits out as well. This is because of connection timeouts, etc. that we had when the load was spiking. The server assigned the work, but the client never got it. I'm looking into implementing a server-side check to confirm work is present, but in the mean time, things will just drop out on their own. Thanks for your patience - it's been a bumpy couple of days, but things seem to be back to normal.


2006-09-09 GMT 22:38    Server Load Spike, 23:00-01:00 UTC

Another load spike occurred this evening - actually higher than any spike we've seen before. Server load hit 598+ at one reading.We took a series of extreme steps to reduce the load in a quick manner, but most things have been returned to normal. Right now, there is a moving target of WU submissions allowed, 80% at the time this is published. We started at 10% 90 minutes ago and things have been working nicely as we increased the share allowed. The logic behind this was to get the clients' back-off timers to activate by holding up the file uploads, which are very server-intensive (the results can be validated once the files arrive).Server setup is moving along, although it will still be a couple days before we move anything. A few items that we ask to help the load: 1) Please do not force the transfer of files or updating to report WU, if at all possible. Allowing BOINC's timers to run helps everyone right now.2)Do not set your caches excessively high (>2 days for a 24/7 connected computer), as the massive reporting of batches of WU jams up the serverAgain, we thank everyone for their patience - we move ever closer to the new server and the benefits of reduced load, etc. that will come with it.


2006-09-10 GMT 02:12    WU Length Doubled

In an attempt to cut our DB problems down, we've doubled the size of the workunits. Now, this only applies to WU not currently in the queue - which means we have about 4 days to go before we hit the new, 500M workunits. Credit will be adjusted accordingly (2x the credit), so there won't be any real change in the amount of work done or the credit, we'll just cut 1/2 of the load on the servers.


2006-09-14 GMT 22:23     Project Back On-Line and Caught Up

On behalf of Lee, myself, and the entire RS community, I'd like to apologize for the server issues we've had over the last three days. It has definitely seemed like every time we solved one problem, three more crept up. As of 22:00 UTC this evening, everything was turned back on and caught up. The backlog of WU returned was validated and processed with no issue by our new, time-set, php-based validator. To recap what happened, a series of cascading server problems (both communication and load) ground things to a halt Monday night into Tuesday. On Tuesday, things ran but jammed up quickly - to counter the load, we turned off file uploads. This worked into Wednesday, when we reversed the system and turned off the scheduler but turned on file uploads. This process remained until 22:00 UTC today, where everything was turned back on. We thank everyone for their patience and support. We're confident that the strict limits we've placed into apache, combined with the load-based restrictors in the PerlBOINC software we've improved on, will carry us up to the changeover to the new server. Thanks again for helping out Riesel Sieve.


2006-9-28 GMT 22:54    Client Version 5.28 Released

With the release of a new Riesel.dat file, we will need to update the current BOINC client from the 5.27 version to 5.28. Not only will there be a slight speed increase (multiply that over 1800 boxes and we'll see a nice speed increase), but we're packing in a couple changes for the 5.28 client. Features: Windows 98/ME Support Reduced debug output (stderr, specifically) New, 69-k DAT file Known Issues: -The client may show a CPU time of 0:00:00 when it checkpoints. If it happens when the unit is finishing, the unit may report a CPU time of 0.00h, but will still get credit since the credit is not time-based. -The Windows 98/ME client will ALWAYS report a CPU Time of 1 hour - from right when it starts until it finishes. While not optimal, it's the only thing I can find, other than shutting off the timer, to get around the built-in BOINC timer that is crashing the client on 98/ME


2006-10-5 GMT 00:21    Site Access Troubles 10/1-10/4

Since completing our server move, we have been experiencing widespread problems accessing any part of the Riesel Sieve project's sites. This error is at the ISP level, and we are working to fix it. Connect rates are slowly getting better as we work through the problem. One workaround is to use the BOINC Manager proxy settings, using a URL of http://boinc.rieselsieve.com and a port of 8000. If you are attached to multiple projects, make sure you suspend them before updating and then turn off the proxy & resume the other projects once you are done. We hope these problems are resolved by late tonight EDT, as some DNS changes we've made should be fully propogated by then. Thanks for your patience and support of the Riesel Sieve project.


2006-10-7 GMT 00:44    Site Connectivity Restored

At about midnight EDT on 10/7/06, connectivity was restored. It took quite a bit of work with the ISP to get things reconfigured, reset, and running - but things are where they should be now.The site started running around 20:00 EDT, but there was many periods of up and down as the ports into the server were turned off, on, off, on, etc as the NOC tested everything. We're still working on some things on the non-BOINC side of the site, but everything for BOINC RS should be fine. Thanks to everyone for their support and continued patience!



2006-10-8 GMT 18:13     Problems Attaching New Hosts

New hosts in the last 7 days have downloaded a blank key file for the Riesel Sieve server. This means that no matter how many times the client tries to download the application files, the client will receive a checksum error and the WU will fail. If you have attached a host to the project any time in October AND cannot successfully download the application files, please detach the host from the project.Once you have detached, please check that your DNS is properly resolving download.rieselsieve.com, and reattach. You should be able to download all files at that point. If you continue to have problems, please visit our forums.



2006-10-15 GMT 23:56    Information for Users Receiving a Misconfigured Host Email

For anyone that receives a "Misconfigured Host" email that refers you to the site for more info, the fix is simple. Your host was attached during the period where our DNS was wrong, so your project md5 key is wrong. To correct this, please detach from the project and reattach. Thank you for your help!



2006-10-22 GMT 00:35     BOINC->phpBB Bridge Created

As you may know, we use phpBB, rather than BOINC's built in forum, as our forum software. Until now, a user had to sign up for BOINC and then for our forums. While not a 100%, on-registration synchronization of the BOINC and phpBB databases, we have taken a step in the right direction. Instead of two separate signups now, you can send over your username and password from the BOINC pages. Click on "Your Account" and then on "phpBB User Sync", and you will be able to set up your phpBB account. One thing to note is that you have to reenter all the information because 1) phpBB allows only 25-character usernames and 2) the passwords are stored differently. All other phpBB settings will need to be done throug the phpBB profile pages, however, as the script is not that advanced. If you have any questions, comments, or troubles, please let us know.


2006-10-23 GMT 00:26    Optimized Sieve Applications Now Available

We have now published a list of EXE files that are official optimized sieve applications depending upon CPU features - CMOV5, CMOV7, SSE2, or non-CMOV. The basic application, CMOV6, is most common, which is why we have ran it so far. These applications will speed up the WU processing, allowing a user to complete more WU per day, and in turn increasing their overall production/score. For details on how to install and the EXE downloads, please see this forum thread: Official Optimized Clients


2006-11-19 GMT 21:49    LLR Test Application Now Available

We have enabled a test application using LLR. In order to crunch LLR workunits, you will need to edit your preferences for Riesel Sieve and "Allow test applications". You can set only P4 clients to run the test application using a venue (home, work, or school), and then they will run LLR as long as work is available. We plan to have processor detection/selection in the near future, but the venues will serve as a temporary workaround. If you have any questions/problems with the new LLR application, please visit the forums.


2006-12-2 GMT 17:19     A New Prime & 5.30 Sieve Released

Congratulations to DarkStar, who found the 742167-digit prime 26773*2^2465343-1 using our "classic" LLR application on Friday. We have verified and submitted the prime, which ranks #20 in the world.As a result, a new, lean, mean riesel.dat is available for download, which requires the release of a new wrapper file as well. 5.30 for windows is being sent out as we speak. There's about 150,000 fewer pairs in the DAT file, thanks to the removal of 72,000 from the k and another 75,000+ from BOINC.Thanks to everyone supporting Riesel Sieve, and here's to another prime!


2006-12-31 GMT 01:46     Year-End Update

As we move to the start of 2007 and mark the end of 2006, I would like to thank everyone who has helped move forward this year. While I don't have space to single out each person, a HUGE thanks to Rytis, from PrimeGrid, for developing the PerlBOINC platform and helping us bring Riesel Sieve to the BOINC platform. A special thank you goes out to AMDave as well, for his work on getting the Sieve to run on Linux via BOINC, and to Lupine1647, for his generous financial contributions that helped us upgrade our servers.Thanks to BOINC, we are sieveing well above 625T, while we began the year around 135T - an astounding accomplishment. In that time, BOINC alone has found over 150,000 factors that have been removed from our DAT file. We have also brought LLR to the BOINC platform, and have successfully double-checked all k/n pairs up to n=500,000, although 650,000 is just around the corner. A thank you goes out to the 2006 Prime Slayers: Maefly (450457), Auritania (196597), bwhite (114487), botXXX (275293), and DarkStar (26773). These 5 primes helped us drop to 68 k's and removed tens of thousands more pairs from the DAT file. As we look to the coming year, I know that I share a common hope with Lee, ceselb, SlangNRox, punchcard, jasong, and the many others who frequent #rieselsieve that we'll see many more k's fall in 2007. With the first-pass LLRNet at 2,500,000+ and BOINC LLR ready to reach that level via double-check in a few months, we'll be able to hopefully see 3,000,000 by year's end. An ambitious goal, I know, but anything is possible as we expand on the BOINC platform. Server reliability, stability, and speed are all areas of improvement for 2007 as well. Our rapid growth has put great strain on our servers, but through the many generous donations (especially from Lupine1647, SlangNRox, and psnow), we've been able to upgrade. The DB server has been upgraded, and we're in the process of upgrading the main web server. BOINC duties are delegated to two servers right now, to help spread the load, and the new webserver will give us 3 boxes to use in the BOINC effort. Thank you to each user who contributed even a few minutes of CPU time to the Riesel Sieve project - it is every WU, factor, and LLR test runs that helps us keep moving. Here's to another prosperous year at Riesel Sieve: to more users, more speed, and most importantly, more primes!


2007-2-4 GMT 11:20      New LLR Beta Application Version Released

We've brought out a new version of the LLR Beta App that should permanently prevent the "popup window" that has surfaced when a WU crashes in certain situations.Because of an error in the XML for the 5.18 version, please abort any 5.18 version WU you get, but allow the 5.19 version to crunch. This should stop the signature verification errors that happened overnight. If you have any questions, please stop by the forums.


2007-2-17 GMT 02:04    New Linux Sieve Version + PPC/Linux Support Added

It's been a busy, but exciting, night at RieselSieve. We finally have a new Linux/x86 version that correctly reports its timing & status to the BOINC client. It also implements sr2sieve, rather than proth_sieve, so users should see a HUGE speedup. We also have introduced a Linux/ppc64 client. This will download from our server automatically, as long as you have compiled BOINC from source on your box. We plan to have a binary available soon. The new, from-source build is necessary because of the version string, powerpc64-unknown-linux-gnu, that it uses. Our server matches that & sends out a TRUE PPC sr2sieve version & wrapper. This also has the corrected linux progress & checkpointing capabilities. Thanks to BlisteringSheep for his help & access to a PPC box for us. As always, please visit the forums to notify us of bugs/changes.


2007-2-21 GMT 00:25    New x86_64 Application Version

Due to some bad compilation flags, the 5.33 application version for x86_64 is excruciatingly slow (~20 hours/WU). We've released a new version that has the correct flags in the sr2sieve app, and the speed that should be there has returned. Updates are pushing out to the x86_64 clients now. This did not affect our other clients.


2007-2-26 GMT 22:11    Connectivity to Asia & Australia Restored

We've been receiving confirmation from users that connectivity to Asia, Australia, and the Pacific have been restored as of this afternoon/evening. Thank you to the numerous people, especially AMDave, Webmaster Yoda, and others, who helped with tracerts, pings, and figuring out where exactly our link to the Internet was having problems. Sorry about the long delay, but it took a lot of testing/convincing to get things fixed.


2007-3-22 GMT 23:49    New Linux Client Version

We have released a new version of our Linux/x86 (5.47) and Linux/x86_64 (5.35) clients. This version brings sr2sieve up to the 1.4.35 version and corrects the "Linux Time Bug" users have been experiencing. The app should now report the correct progress, status, and CPU times throughout the workunit. This will prevent the client DCF from plummetting when running the linux client. As always, please direct questions to the forum.

评分

参与人数 1基本分 +10 收起 理由
霊烏路 空 + 10

查看全部评分

回复

使用道具 举报

 楼主| 发表于 2008-2-8 18:45:53 | 显示全部楼层
nnd,还有字数要求~愣是说我的帖子过长~~


2007-4-1 GMT 00:44    200,000 Factors + 200,000 LLR Tests

Thanks to the continuing support of our growing userbase, we have found our 200,000th factor with the BOINC platform. This is a huge milestone, and we thank everyone that has helped us get there. At the same time, we are just over a day from our 200,000th LLR test - another milestone. We are just under completing all tests up to 1.1 million, so we're about 42% of the way to our current first-pass level. At the current rate of 1000 tests/day or so, it will still be a couple months. Thanks to everyone who is helping with the beta effort.


2007-4-1 GMT 00:54    Upcoming Project Maintenance

This week will be a week of ongoing maintenance for the project. Each day, maintenance will be conducted during the period 1300 EDT - 2100 EDT (1700 UTC - 0100 UTC). During this time, there may be periods where one or more project servers will be unavailable. During these times, please check the Maintenance Forum Thread for the latest info on what is or isn't available. Thank you in advance for your patience - this work will help us improve everything on our BOINC side.


2007-4-10 GMT 23:00   185 Problem LLR WU Identified

A problem has been identified with 185 regenerated WU. This has crossed their output information and made it nearly impossible to process them. Please see this forum thread for more details. No currently running LLR WU is affected by this problem - it only affected workunits that may be pending in your account. The WU affected are in the range WU id 2081361 - 2118389 and have result names of the form "riesel-llr_######_#" . Thanks for your patience & understanding as we try to repair these WU.


2007-4-14 GMT 04:31    Planned Power Outage, April 21

Our electric company has notified us that there will be a power outage for our building on April 21st from 8am - 4pm EDT. This outage is to replace the feed lines and transformers for the building. The project and all services will be down during that period. We will have some extra work on hand if people feel the urge to bump queues up (slightly) to account for that outage. Thanks in advance for your patience and understanding.


2007-4-17 GMT 20:54    Problem With Sieve WU 4-17-07

Today was the first day we started handing out WU above 1000T. Unfortunately, the WU were still coded for 47-byte WU files. Since we went above 1000T, the WU files are now 49 bytes long. This caused the WU file handling problems from about 10AM EDT on. Those WU have all been deleted and recreated. We now have the correct WU running from this batch. We apologize for the problems in getting work today.


2007-4-18 GMT 23:45     Continuing Sieve App Problems 4-18

The sieve app is not cooperating with the new, 1000T+ WU. A new version was released this evening (5.31) that disables the progress reporting code. CPU Time will accurately increase, but the % done will remain at 0 for the length of the WU. We apologize for that - hopefully, a new version will come out by Friday with the new (correct) code. This switch-off was needed to bring the app back online.


2007-4-22 GMT 23:01    New Sieve App Release for Windows

-------Windows/x86 & Windows/x86_64 Verison 5.32------- Known Bugs: We don't have the same checkpoint logic as the linux apps, as Windows doesn't support process signals. We are working on a true solution. Right now, checkpoints will occur every 5 minutes. Having "leave apps in memory while suspended" caused the app to hang in 1 trial (out of 4, on the same box). I'm looking into it. Similarly, in certain cases, the sieve app did not always get properly closed when boinc was being closed. Bugs Fixed: Problems associated with the 5.31 release - including no progress reporting, some app suspension handling, etc. Fixes handling of 1000T+ WU properly. Note: this is the first windows app to include sr2sieve. We will be putting out a new set of optimized sieve apps, catered to different architectures. This is the athlon-tuned, SSE2-enabled (when CPU has it) edition. A true 64 bit client is coming - I have to get mingw running 64-bit first. Report bugs & problems here, as usual.


2007-4-24 GMT 00:06    Abort 5.32 Sieve WU on Windows

Users with 5.32 series WU on Windows should abort the WU. The 5.32 client does not properly report its status as "finished", which causes an endless loop for the sieve. Version 5.33 has been released which fixes this problem. Please visit the forums for more information.


2007-4-24 GMT 23:22    New Day, New Client for Sieve + Good News

Version 5.34 of the Sieve has been released. I'm hoping this is the last release required to stomp out this loop bug that is plaguing the sieve. I'm already starting work on a pseudo-wrapper that will only have one executable file, limiting how much has to be updated when we need to make changes. I also hope that it will bring us closer to a true native BOINC app. On the good news side of things, a possible prime is undergoing internal verification - it would be the 19th largest in the world if it comes back prime. A prime would cause the release of version 5.35, with a new DAT, later this week. Thank you all for your help and patience these last two weeks - the variety of problems has kept us all very busy. In the end, I promise, things will be for the better.


2007-4-28 GMT 12:10    Back to 5.31 Sieve Temporarily

Temporarily, we've had to go back to the 5.31 sieve version. We cannot get 5.32-5.34 working correctly, so 5.31 is the "last working" version. It does not checkpoint, and it is actually the checkpoints themselves causing the problems in 5.32-5.34 I've found. Once I have this hammered out, we'll be back on track.


2007-4-30 GMT 00:32    Prime Found - and a New DAT Version

Congratulations to Cipher, who found his 2nd prime with the Riesel Sieve Project. While not a BOINC prime, this LLRNet beast weighed in at #19 in the world - 794,556 digits long. 342673*2^2639439-1 is indeed prime. Thank you to everyone that has made this prime possible. I'm also pleased to announce the 5.35 release of the Windows client. This is a real bugfix, as watzkej has been gracious enough to spend most of the evening in #rieselsieve debug testing things, and Chuck has helped narrow down all my bad coding problems (that he could find). We're on track again with this 5.35 release and should see a speed increase - both from the smaller dat (about 200,000 pairs, between the Sieve effort and removing 1 k) and the use of sr2sieve. Thanks for sticking with us this last week - it has been quite a hectic time for all of us.


2007-5-10 GMT 07:19    New Linux Clients

A new x86 and x86_64 set of linux clients has been sent out to the hosts. It includes the new DAT file, updated sr2sieve, and a new wrapper format that will allow us to interchange what is run in the wrapper more easily. Look for the PPC build to come out this evening. As always - send any questions over to the forums.


2007-5-14 GMT 23:39    New LLR Client Version

We're pleased to announce the 5.20 series of LLR clients. This is the first in a series of upgrades & updates we plan to make in the next 1-2 weeks. This introduces the new wrapper format to the Windows OS - it has worked extremely well on Linux, so we're hoping to duplicate those successes. Internal testing over the weekend went well. Two main breakthroughs with this new wrapper: (1) no more 0.00 CPU time LLR WU. (2) (hopefully) No more random queue crash for LLR WU. As long as (2) does not creep up this week - please monitor your hosts - we will move forward with our plans to make LLR more of a project-wide priority.The LLR executable itself stays the same, we are only changing the wrapper and introducing a job file.Please make sure that you notify us of any queue troubles or other issues with the wrapper (or just drop in and tell us how great it is). Thanks in advance!


2007-5-19 GMT 15:35    Credit Changes Poll

We are currently evaluating our credit system, in light of the recent speed-up in sieve (5.36 Windows/5.50 Linux) and the continuing effort to improve LLR scores. The input from our users will lead the discussion of the new credit levels and the basic alignment between sieve and LLR scores (finally). Please consider taking a moment to visit our fourms and casting a vote. Remember that if you have a BOINC username, you do not have to register for the forums. Just use your BOINC username and password to log in and vote. This poll will run until Thursday, 5/24.


2007-5-25 GMT 22:55    LLR Validation Stopped

It was brought to our attention by psnow that a problem existed in the LLR validator - computers were getting granted 4, 5 or even 6 times the credit that they should. At about 8:30 pm, we halted all validation - once it was confirmed that only LLR was affected by the problem, we turned back on sieve validation. We plan to have the LLR validator up and running again Saturday afternoon or evening. More details can be found on our progress in this thread.


2007-6-4 GMT 23:23     Massive Work Problems

You make the mistake of stepping out for 2 days and WOW - things just go up in flames. Sieve was out of whack since Saturday PM, with WU getting reserved & going nowhere except /dev/null once the BOINC client downloaded them. I purged out all those bad WU and have started testing the new ones to make sure they work properly. See this forum thread for more information. We did run LLR project-wide for about an hour or so. This created about a 5,000 WU validation backlog on top of the 1200 or so that were already waiting. Since this is on the validation side of things, expect the backlog to last into (at least) tomorrow. Should be interesting to get the results on how well they ran. Thanks to watzkej who acted as the mass communicator in my absence and to Lee for trying to get things back up and running last night. No luck though. Last few of my tests should be done within an hour or so, which means we'll get back to work.


2007-6-7 GMT 01:04    Smooth Running Again

Things are running smooth again. About 73% of the backlogged LLR WU's have validated first-shot, another 23% were inconclusive. While this is fairly high, I am not surprised, as much of this work that is inconclusive came during that temporary switch we made. I'm examining those WU and looking into what's up. Overall, the validation of all that work has gone nicely. Sieve WU are also up and running since Monday night, without a hitch. Things are back to normal. We hope to have a linux version of LLR by week's end, thanks to watzkej. We'll see if that ends up being possible, things are in testing now. Thanks to everyone for their support.


2007-6-8 GMT 13:21    Work Problems June 10th

This morning, a bad sieve range was fed into the work generator. This created about a 6-hour period of repeatedly bad work. We have fixed the work generation, although workunits will now be 1G for sieve, which is 2x as long as the "old" workunits. We have adjusted crediting to account for this. The latest info regarding the problems that were created and the current status on the servers can be found in the forums.


2007-6-26 GMT 18:26    Linux LLR Now Available

LLR testing is now available on Linux. Make sure that you have "Allow test applications" enabled for your host and you will receive LLR workunits. If you have questions, please visit the forums.


2007-7-11 GMT 11:42    LLR Focus on k=141941

Lee and I are determined to defeat k=141941, our largest k. He feels that there was a missed prime somewhere for this k, so we're going to turn all of our attention - LLRNet AND BOINC LLR to this one k. LLRNet will go up to 5 million, BOINC LLR will do the re-check from the current level (about 1.5M) to 3.0M. To rally the troops, all Linux BOINC clients will get LLR work (we're confident that the scoring has been balanced finally, but will still monitor closely). We are also encouraging windows users to switch over to LLR if possible. LLRNet has about 4000 pairs to do before the k=141941 assault truly begins, and BOINC has about 1400. Here's to slaying another k!


2007-8-2 GMT 02:16    LLR Workunit Problem

LLR workunits above 3.0M have a timing problem where many processors error out with "max CPU time exceeded". Please abort any workunit above the 3.0M threshold on boxes 1.5GHz or higher, and above 2.90M for boxes below 1.5GHz. These WU will be regenerated at a later date. Workunits are also being made now (3.17M or higher), which are OK. Please let those go. Please direct questions/comments/rants at Bryan to the forums.


2007-8-15 GMT 01:13    Please Update Old Clients

Please update your BOINC core clients. There are a number of 5.4.9 clients (and others in the 5.4.x series) that are causing a number of the WU errors we're seeing. Please update to the 5.10.x clients (latest recommended version), as we hope will help us narrow down some of the client issues we're having.


2007-9-7 GMT 22:44     Status Update 10-21

Lee and I wanted to post a notice and let everyone know that things are running well - so, we're going to start making some changes.k=141941 is about 30 tests away from being tested to n=2^22 - far beyond the other k's we are testing. Unfortunately, a prime has not yet been yielded. We are examining where we want LLR to go next. For the time being, the shorter, double-check workunits are being run.In the next week or so, we will be migrating from PerlBOINC to 'true' BOINC. While we do not anticipate any major problems or items of notice to the users, there may be small periods of downtime while we switch. We'll make every effort to post them in the forums beforehand. Some extra features, like the sieve & llr range pages, may not be updated or available during the transition.We are also planning to release all new clients when we switch to the new server code. Linux 64-bit sieve will return, and we will be upgrading all the sieve clients to the latest versions of sr2sieve, with the goal of an additional speed improvement. We also will release a new DAT file for sieve at that time. LLR will receive a new wrapper, with the hopes of finally nailing the dreaded queue crash bug.All in all, it should be a busy (and much more exciting) next couple of weeks - stay tuned for details!


2007-10-28 GMT 01:01    Riesel Sieve Finds its First BOINC Prime!

Congratulations to Mackerel, who had a box turn in our first BOINC Prime this evening. The k is 469949, a relatively light k at about 29,000 k/n pairs removed. However, the test was a missed test on 1st run, highlighting the need for a proper double-check by BOINC.We will release the full k/n pair after it is submitted to PrimePages, but it does weigh in at just over 496,000 digits. Is there another double-check prime out there? Only way to find out is to run LLR and help us hunt down the remaining 66 k's. Thank you to all the participants for helping us bring down the workload, and a special thanks to Mackerel for killing his second k.Manual sieveing DAT file will be released in the morning; the new DAT for BOINC will be released as part of our server switch.

BOINC 平台的 Riesel Sieve 找到了第一个质数


2008-1-16 GMT 8:54    BOINC Credit Discussion

Over the last few days, there has been quite a number of discussions regarding the current BOINC credit model, as well as several proposals for new models to follow. While some of the discussion has taken place on the boinc_projects list, many of these discussions have occurred on IRC, multiple project/team/BOINC forums, or personal email. In the interest of time, clarity, and the ability to hear many views in a single arena, the staff of Riesel Sieve and I would like to extend an invitation to a BOINC Credit Community Discussion on Monday, January 21st. This discussion will be held via irc on irc.freenode.net, in the channel #boinc-credit. In the interest of having the discussion at a time conducive to all, we will be hosting two discussions, at 2pm US Eastern Time and 8pm US Eastern Time. Please consider attending either or both. The logs from each will also be posted on the Riesel Sieve website shortly afterward, to allow those who could not attend the opportunity to review the transcript. The only way that we can come to a true solution to the crediting situation is through a thorough discussion (or series of discussions) in a real-time format, not over email. Anyone from the BOINC community, including individual users, is invited to attend. Please consider redistributing through your own team channels to encourage attendance.

关于 BOINC 积分的讨论
在irc上将有关于BOINC积分的说明~已过期~

评分

参与人数 1基本分 +10 维基拼图 +2 收起 理由
霊烏路 空 + 10 + 2

查看全部评分

回复

使用道具 举报

发表于 2008-2-8 20:08:18 | 显示全部楼层
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 新注册用户

本版积分规则

论坛官方淘宝店开业啦~

Archiver|手机版|小黑屋|中国分布式计算总站 ( 沪ICP备05042587号 )

GMT+8, 2024-3-29 00:32

Powered by Discuz! X3.5

© 2001-2024 Discuz! Team.

快速回复 返回顶部 返回列表