Posts by Jake Weiss

1) Message boards : News : 30 Workunit Limit Per Request - Fix Implemented (Message 68609) Posted 26 Apr 2019 by Jake Weiss Post: Thank you Keith, Glad to know its likely an issue with a client and likely not with us. We are running server 1.0.4. Best, Jake
2) Message boards : News : Leaving MilkyWay@home (Message 68596) Posted 25 Apr 2019 by Jake Weiss Post: Hey Everyone, I want to thank you all for your support and encouragement over the last 7 or so years that I have been a developer and scientist on this project. Unfortunately, it has come time for me to move on to the next phase in my life and career. Tuesday, April 30th will be my last day working in an official capacity on the MilkyWay@home project and for RPI. Over the last several months, I have been doing my best to document and pass my knowledge down to the current MilkyWay@home scientists and developers, so I am confident you all will be in good hands. I wish you all the best, and thank you all again. Best, Jake
3) Message boards : News : 30 Workunit Limit Per Request - Fix Implemented (Message 68594) Posted 25 Apr 2019 by Jake Weiss Post: Hey Keith, Thanks for chiming in. Can you just clear up for me, is this a problem with one of our server settings or is this a client bug? Thanks, Jake
4) Message boards : News : New runs of MilkyWay Nbody out (Message 68588) Posted 24 Apr 2019 by Jake Weiss Post: Glad I could help! Best, Jake
5) Message boards : News : New runs of MilkyWay Nbody out (Message 68586) Posted 24 Apr 2019 by Jake Weiss Post: We can cancel all of these workunits and abort them on the server side. I'll do that now. The only ones that should be erroring are those which haven't cleared the work queue yet. Sorry about that. Best, Jake
6) Message boards : Number crunching : 1.76 Milkyway N-Body Aborting (Message 68577) Posted 23 Apr 2019 by Jake Weiss Post: Hey Everyone, Sorry, this is my fault. I told Eric to release the new version of Nbody before we were ready to put up new runs. This version is not backwards compatible with our old runs so it caused a bunch of errors. We have new runs up now that should be compatible with the new version. If you see any errors with these new runs, there will be a new post that you can put your errors in. Sorry again. Best, Jake
7) Message boards : News : New version of MilkyWay Nbody (Message 68576) Posted 23 Apr 2019 by Jake Weiss Post: Sorry guys, this is my fault. I told him to release the new version before we were ready to put runs up and I didn't realize that Nbody had backwards compatibility issues. We are working on a new run and should have it up within an hour or two. Best, Jake
8) Message boards : Number crunching : WUs not downloaded in time - rig is idling - doing no work ... (Message 68561) Posted 18 Apr 2019 by Jake Weiss Post: Hey Everyone, This is a known issue, but I have not been able to find a solution to the problem. It's probably an obscure configuration issue or something, but unfortunately they are very hard to track down. Maybe I'll try a post on the BOINC official forums and see if this is a know issue with a specific configuration. Best, Jake
9) Message boards : Number crunching : NoContraintsWithDisk200 vs. south4s (or whatever) (Message 68549) Posted 16 Apr 2019 by Jake Weiss Post: Hey Everyone, Part of this issue is probably mine and Tom's fault. We forgot to change the number of workunits we bundle together when we increased the number of parameters in our model for these runs. We will put up new runs ASAP which have a smaller bundle size and should nolonger crash on machines with smaller commandline sizes. So sorry about that. Best, Jake
10) Message boards : News : 30 Workunit Limit Per Request - Fix Implemented (Message 68514) Posted 11 Apr 2019 by Jake Weiss Post: Hey Everyone, I bumped up the number of workunits allowed at any given time a little bit. Let me know if that helps. Jake
11) Message boards : News : 30 Workunit Limit Per Request - Fix Implemented (Message 68508) Posted 10 Apr 2019 by Jake Weiss Post: Hey Vortac, I'm equally stumped here. My only thought is that sometimes we get unlucky and you request work when another group of people have also request/before the feeder can refill the queue. I'm going to do a little thinking before I try to implement any solutions to this issue for now. Best, Jake
12) Message boards : News : 30 Workunit Limit Per Request - Fix Implemented (Message 68499) Posted 10 Apr 2019 by Jake Weiss Post: I'll bump the RPC delay up to 3 minutes. If this is too long, let me know. Best, Jake
13) Message boards : News : 30 Workunit Limit Per Request - Fix Implemented (Message 68495) Posted 9 Apr 2019 by Jake Weiss Post: Hey Manfred, Most of these solutions were implemented with GPUs in mind and are limited to GPUs. I'll take a look at the number of CPU workunits currently allowed and maybe try doubling it. Best, Jake
14) Message boards : News : 30 Workunit Limit Per Request - Fix Implemented (Message 68493) Posted 9 Apr 2019 by Jake Weiss Post: Hey Everyone, I see that the rpc_delay what not set to 90 seconds as I thought. I have updated this accordingly. Hopefully this will solve our issues. Best, Jake
15) Message boards : News : 30 Workunit Limit Per Request - Fix Implemented (Message 68492) Posted 9 Apr 2019 by Jake Weiss Post: Hey Everyone, Sorry I didn't had a chance to reply last week. I was at a conference sharing some of the great new results we have. I am back now so I am going to start reading through this thread to see what I can do to fix this issue on my end. I saw that some people were suggesting changing the rpc_delay which I think we have set to 90 seconds. I'll post again soon when I put a plan together. Jake
16) Message boards : News : 30 Workunit Limit Per Request - Fix Implemented (Message 68444) Posted 28 Mar 2019 by Jake Weiss Post: I'm not sure how to force the client to download new work when it returns workunits to the scheduler. I've been searching the BOINC documentation looking for flags to try, but I can't find anything. Anyone have any suggestions? Jake
17) Message boards : News : 30 Workunit Limit Per Request - Fix Implemented (Message 68441) Posted 28 Mar 2019 by Jake Weiss Post: Hey guys, So the current set up allows for users to have up to 200 workunits per GPU on their computer and another 40 workunits per CPU with a maximum of 600 possible workunits. On the server, we try to store a cache of 10,000 workunits. Sometimes when a lot of people request work all at the same time, this cache will run low. So all of the numbers I have listed are tunable. What would you guys recommend for changes to these numbers? Jake
18) Message boards : Number crunching : Abandoned task? (Message 68431) Posted 27 Mar 2019 by Jake Weiss Post: That is really strange because other people have gone on to compute those two specific workunits and it was able to validate. Maybe it's an issue with the BOINC client version you are using? I'm really stumped here. Jake
19) Message boards : News : 30 Workunit Limit Per Request - Fix Implemented (Message 68430) Posted 27 Mar 2019 by Jake Weiss Post: Hey wb8ili, Can you give it another try for me and let me know what you see? Best, Jake
20) Message boards : News : 30 Workunit Limit Per Request - Fix Implemented (Message 68428) Posted 27 Mar 2019 by Jake Weiss Post: Hey Everyone, Some users were only able to request 30 workunits at a time max. This is far too low to ensure optimal GPU usage. We have increased the feeder's shared memory size to hopefully increase the number of workunits available to request at any given time. Please let me know here if this has helped the issue. Best, Jake

Next 20