I think we'll be able to do it. The workunits this year are worth more, from what I'm seeing it's about 50%. Last year I was averaging 500k ppd with a 3800x and a r9 390, and before I found my 7950 f@h was estimating my ppd at 800k. Right now my total estimated ppd is 1.1 million, 281k with 13...
I had mine set to any disease but I would often get some cancer research work that would drop my ppd by 250k. So far my ppd is staying around 1 million with Alzheimer's and I actually prefer to contribute to Alzheimer's research.
CPUs:
1998 Pentium II @300MHz
2003 Athlon XP 2500+
2006 Athlon 64 3400+
2009 Core 2 Quad Q9400
2012 Core i7 3770k
2019 Ryzen 7 3800X
GPUs:
1998 ATI Rage Pro
2003 Radeon 9600
2009 Radeon HD 4830
2011Radeon HD 5850
2013 Radeon HD 7950
2015 Radeon R9 390
First one that I started crunching with...
Count me in. All I will have this year is a r9 390, might be able to start up a 7950 later once I finish building a new ryzen build in a week or two. Will be running most of the month, won't be able to crunch when I get all of my parts together for the new build. I'm guessing around 300K ppd...
Count me in. I'm also salvorhardin on f@h. My output will be similar to last years. Right now I only have my 7950 running and I'm hoping to fix my r9-390 within the next week.
To ignore specific cards in boinc you'll need to edit/create a cc_config.xml file in ProgramData/Boinc folder. I attached what should work with nvidia cards, with N being the device number. Just exit boinc and edit/create the file and then start boinc. When you go into you event log in boinc...
On a stock i7-3770K with hyperthreading disabled and all cpus free:
Stock 7950 (860/1250) 56.48s with 11.45s cpu time (20 workunits averaged)
Stock R9 390 (1015/1500) 60.72s with 13.14 cpu time (17 workunits averaged)
There's moowrapper, einstein, milkyway and f@h. Those are the main ones I can think of. Have you optimized your settings in collatz to see how much ppd you can manage? I'm currently running collatz and was able to cut my wu times by almost half. I think I might end up at 7 million ppd from a r9...
Thanks for the stats petrusbroder. It's nice seeing all of the stats in one place. For some reason I'm not showing up as crunching in 2007. I checked the final stats for that race and I'm missing from the total stats but show up in the weekly production.
yeah, basically to force which application is used. From what I can gather the milkyway servers can't properly detect newer amd cards and you need an app info file in order to get work. Once they update the boinc version on the servers then it shouldn't be a problem.
Basically, from what I gather there will be a major release each year with minor updates throughout the year. Last year was omega, this year it's crimson. The control center is much faster at starting up and has more options. I forgot to mention that I had to use an app info in order to get work...
It should be able to, a few years ago I had a 4830 and 5850 both running on the same rig without doing anything special. Each gpu is assigned it's own slot with it's own options.
Sorry, yeah it's universe I was talking about. At first I thought it was the cumulative update in windows 10 that screwed it up, but after checking my update history I saw my last installed update was 2 days before it added time.
Now back to wasting 20s before starting each milkyway workunit. Looks like we'll gain 2 points in milkyway within 24hrs. We're about a million behind and we're being out produced by about 140k a day.
Sorry, it's the windows 10 fall update, I got it throuch windows update. Currently have milkyway settings set at only accepting milkyway@home workunits, left n-body and separation unchecked and unchecked to send me workunits from other projects.
Upgraded to the fall update today and it appears that the wasted cpu time is fixed. I'm now crunching 2 milkyway opencl workunits at a time in under a minute.
I've been having the same problems on my machines. Tried switching to different milkyway apps but it only fixed it for 2 wus and then it started increasing the time to complete. Only thing that seems strange is that it runs the cpu at the beginning of the wu and not at the end.
The lunatics app installs optimized applications for seti, allowing you to crunch regular seti wus with applications designed around your cpu (sse3, avx) and/or gpu (opencl, cuda, intel). Over 40 wus the optimized apps ran about a third faster than the normal application.
In the last few days I've been running seti with both the stock app and the lunatics app. With 40 workunits I averaged a ppd of 6333 on the stock app and I averaged 8888 ppd using the lunatics installer(v43b). Both were run on a 3770k at stock speeds with all 8 cores. I wasn't able to compare...
I also have a nexus 7 (2013) LTE, It has qi wireless charging. You might try to wirelessly charge it to see if it's the microusb port that is damaged. If it's the port you can wirelessly charge it until you have it fixed.
I don't think it will be software, more than likely it's your usb connector on the nexus. You've tried other cables and power bricks so that narrows it down to the tablet itself. Have you tried using a wireless charger?
By default it erases everything on the phone. If you open the bat file with notepad and remove the "-w" from the file it allows you to upgrade without erasing your files.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.