Welcome to MilkyWay@home

Posts by mikey

1) Questions and Answers : Unix/Linux : Compute errors (Message 74984)
Posted 23 hours ago by Profilemikey
Post:
@mikey

Thanks for the hint.


As the 528 driver is still only available for win10+ at the moment I tried to switch to 515.


For me this works better.


Last messages sent:

Mi 01 Feb 2023 11:32:40 | | Starting BOINC client version 7.20.5 for x86_64-pc-linux-gnu
Mi 01 Feb 2023 11:32:40 | | This a development version of BOINC and may not function properly
Mi 01 Feb 2023 11:32:40 | | log flags: file_xfer, sched_ops, task
Mi 01 Feb 2023 11:32:40 | | Libraries: libcurl/7.68.0 OpenSSL/1.1.1f zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.2.0) libssh/0.9.3/openssl/zlib nghttp2/1.40.0 librtmp/2.3
Mi 01 Feb 2023 11:32:40 | | Data directory: /var/lib/boinc-client
Mi 01 Feb 2023 11:32:41 | | CUDA: NVIDIA GPU 0: NVIDIA GeForce RTX 2070 (driver version 515.86, CUDA version 11.7, compute capability 7.5, 7974MB, 7974MB available, 6705 GFLOPS peak)
Mi 01 Feb 2023 11:32:41 | | OpenCL: NVIDIA GPU 0: NVIDIA GeForce RTX 2070 (driver version 515.86.01, device version OpenCL 3.0 CUDA, 7974MB, 7974MB available, 6705 GFLOPS peak)
Mi 01 Feb 2023 11:32:41 | | libc: version 2.31
Mi 01 Feb 2023 11:32:41 | | Host name: mobile-workstation
Mi 01 Feb 2023 11:32:41 | | Processor: 24 AuthenticAMD AMD Ryzen 9 PRO 3900 12-Core Processor [Family 23 Model 113 Stepping 0]
Mi 01 Feb 2023 11:32:41 | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip rdpid overflow_recov succor smca sme sev sev_es
Mi 01 Feb 2023 11:32:41 | | OS: Linux Ubuntu: Ubuntu 20.04.3 LTS [5.13.0-44-generic|libc 2.31]
Mi 01 Feb 2023 11:32:41 | | Memory: 31.25 GB physical, 32.00 GB virtual
Mi 01 Feb 2023 11:32:41 | | Disk: 786.29 GB total, 91.39 GB free
Mi 01 Feb 2023 11:32:41 | | Local time is UTC +1 hours
Mi 01 Feb 2023 11:32:41 | | VirtualBox version: 6.1.42r155177
Mi 01 Feb 2023 11:32:41 | | Config: GUI RPCs allowed from:
Mi 01 Feb 2023 11:32:41 | | Reading preferences override file
Mi 01 Feb 2023 11:32:41 | | Preferences:
Mi 01 Feb 2023 11:32:41 | | max memory usage when active: 15997.71 MB
Mi 01 Feb 2023 11:32:41 | | max memory usage when idle: 28795.87 MB
Mi 01 Feb 2023 11:32:42 | | max disk usage: 50.00 GB
Mi 01 Feb 2023 11:32:42 | | max CPUs used: 2
Mi 01 Feb 2023 11:32:42 | | suspend work if non-BOINC CPU load exceeds 51%
Mi 01 Feb 2023 11:32:42 | | (to change preferences, visit a project web site or select Preferences in the Manager)
Mi 01 Feb 2023 11:32:42 | | Setting up project and slot directories
Mi 01 Feb 2023 11:32:42 | | Checking active tasks
Mi 01 Feb 2023 11:32:42 | Milkyway@Home | URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 922489; resource share 100
Mi 01 Feb 2023 11:32:42 | | Setting up GUI RPC socket
Mi 01 Feb 2023 11:32:42 | | Checking presence of 176 project files
Mi 01 Feb 2023 11:32:42 | Milkyway@Home | Fetching scheduler list
Mi 01 Feb 2023 11:32:44 | Milkyway@Home | Master file download succeeded
Mi 01 Feb 2023 11:32:50 | Milkyway@Home | Sending scheduler request: To report completed tasks.
Mi 01 Feb 2023 11:32:50 | Milkyway@Home | Reporting 81 completed tasks
Mi 01 Feb 2023 11:32:50 | Milkyway@Home | Not requesting tasks: don't need (CPU: not highest priority project; NVIDIA GPU: job cache full)
Mi 01 Feb 2023 11:32:53 | Milkyway@Home | Scheduler request completed
Mi 01 Feb 2023 11:32:53 | Milkyway@Home | Project requested delay of 91 seconds
Mi 01 Feb 2023 11:34:25 | Milkyway@Home | Sending scheduler request: To fetch work.
Mi 01 Feb 2023 11:34:25 | Milkyway@Home | Requesting new tasks for CPU and NVIDIA GPU
Mi 01 Feb 2023 11:34:28 | Milkyway@Home | Scheduler request completed: got 101 new tasks
Mi 01 Feb 2023 11:34:28 | Milkyway@Home | Project requested delay of 91 seconds
Mi 01 Feb 2023 11:34:30 | Milkyway@Home | Started download of milkyway_nbody_1.82_x86_64-pc-linux-gnu__mt
Mi 01 Feb 2023 11:34:30 | Milkyway@Home | Started download of milkyway_1.46_x86_64-pc-linux-gnu
Mi 01 Feb 2023 11:34:30 | Milkyway@Home | Starting task de_modfit_85_bundle5_3s_south_pt2_2_1674667491_9782447_0
Mi 01 Feb 2023 11:34:32 | Milkyway@Home | Finished download of milkyway_1.46_x86_64-pc-linux-gnu
Mi 01 Feb 2023 11:34:32 | Milkyway@Home | Started download of parameters-81-southpt2.txt
Mi 01 Feb 2023 11:34:32 | Milkyway@Home | Starting task de_modfit_73_bundle5_3s_south_pt2_2_1674667491_9781822_0
Mi 01 Feb 2023 11:34:32 | Milkyway@Home | Starting task de_modfit_73_bundle5_3s_south_pt2_2_1674667491_9781821_0
Mi 01 Feb 2023 11:34:33 | Milkyway@Home | Finished download of milkyway_nbody_1.82_x86_64-pc-linux-gnu__mt
Mi 01 Feb 2023 11:34:33 | Milkyway@Home | Finished download of parameters-81-southpt2.txt
Mi 01 Feb 2023 11:34:33 | Milkyway@Home | Started download of stars-81_pt2.txt
Mi 01 Feb 2023 11:34:33 | Milkyway@Home | Started download of parameters-71-southpt2.txt
Mi 01 Feb 2023 11:34:35 | Milkyway@Home | Finished download of parameters-71-southpt2.txt
Mi 01 Feb 2023 11:34:35 | Milkyway@Home | Started download of stars-71_pt2.txt
Mi 01 Feb 2023 11:34:36 | Milkyway@Home | Finished download of stars-81_pt2.txt
Mi 01 Feb 2023 11:34:36 | Milkyway@Home | Finished download of stars-71_pt2.txt
Mi 01 Feb 2023 11:34:36 | Milkyway@Home | Started download of EMD_v176_newdata4.lua
Mi 01 Feb 2023 11:34:36 | Milkyway@Home | Started download of data_hist_summer_2020_beta_disp7.hist
Mi 01 Feb 2023 11:34:37 | Milkyway@Home | Finished download of EMD_v176_newdata4.lua
Mi 01 Feb 2023 11:34:37 | Milkyway@Home | Finished download of data_hist_summer_2020_beta_disp7.hist
Mi 01 Feb 2023 11:34:37 | Milkyway@Home | Started download of EMD_v182_newpotential.lua
Mi 01 Feb 2023 11:34:38 | Milkyway@Home | Finished download of EMD_v182_newpotential.lua
Mi 01 Feb 2023 11:37:23 | Milkyway@Home | Computation for task de_modfit_85_bundle5_3s_south_pt2_2_1674667491_9782447_0 finished
Mi 01 Feb 2023 11:37:23 | Milkyway@Home | Starting task de_modfit_85_bundle5_3s_south_pt2_2_1674667491_9782478_0
Mi 01 Feb 2023 11:40:27 | Milkyway@Home | Computation for task de_modfit_85_bundle5_3s_south_pt2_2_1674667491_9782478_0 finished
Mi 01 Feb 2023 11:40:27 | Milkyway@Home | Starting task de_modfit_84_bundle5_3s_south_pt2_2_1674667491_9782438_0


As long as it's working it's a good thing!!!
2) Questions and Answers : Windows : Make any "C:" drive run BOINC from a central location (Message 74983)
Posted 1 day ago by Profilemikey
Post:
Thanks, Link!

I think I'll continue to ponder this idea some more before starting the "experiment". If I do proceed, I'll try to start as simply as possible and report what happens.

Martin


If you are thinking of downloading tasks on one pc and then running them on a different pc there are safeguards against doing that as it's one of the ways people used to cheat big time back when Seti was young. YES there are people that do it today but I don't know how or if it's allowed or ignored at certain projects.
3) Questions and Answers : Unix/Linux : Compute errors (Message 74975)
Posted 1 day ago by Profilemikey
Post:
Computation error after a few seconds when starting Milkyway@home Separation 1.46 (opencl_nvidia_101)



I always get:



Application
Milkyway@home Separation 1.46 (opencl_nvidia_101)
Name
de_modfit_83_bundle5_3s_south_pt2_2_1674667491_8394156
State
derivation error ( sorry for the simple translation, I'm using the german version)
Di 31 Jän 2023 12:19:57
Expiry date
So 12 Feb 2023 12:19:56

ressources
0.957 CPUs + 1 NVIDIA GPU
approximate derivation needed
42.064 GFLOPs
process-time
00:00:00
elapsed time:
00:00:02

executable file
milkyway_1.46_x86_64-pc-linux-gnu__opencl_nvidia_101


Does anyone know why this is happening all the time?
cheers
Niko


One thing you might try is updating to the latest Nvidia drivers, you are running version 510 and version 528 is out now, just be sure to skip the 525 and 526 versions as they caused problems at some Boinc Projects.
4) Message boards : Number crunching : Future of Milkyway@Home (Message 74974)
Posted 1 day ago by Profilemikey
Post:
Agreed it depends on those who wish to target Milkyway@Home over other projects that don't require DP.
Not sure about people (ie - the masses) buying Tesla's & Instinct cards. I guess time will tell.
I can't dedicate my NVIDIA cards to M@H though. The credits are just too low and those cards for me personally are better used elsewhere.

Great discussion. Thank you


I have a question for you...you say you want to crunch for projects that give alot of credit for their tasks and you DO have a bit over 21 Billion credits already so my question is what are you going to do with them? As you can see from my own signature I'm working on my second Trillion credits but I STILL can't buy a cup of coffee with them at Starbucks or a Dunkin Donut store!! YES credits are nice but it can't be the sole reason for crunching someplace.

Seti did research on credits one time and came up with a few things that projects must consider when giving out credits for their tasks, they concluded that giving out more credits increases the likelihood of more users coming to your project which also brings more cheaters so your anti-cheating systems have to be robust or alot of the work done is suspect. Another thing all those users coming to your projects is that the network can be overwhelmed, just ask World Community Grid about that right now, and can have a negative effect on your project for a long time. And giving out more credits than other projects for your tasks increases the need for a more robust supply of tasks to meet the new demand. In short giving out more credits is a two edged sword for projects whole like MiklyWay operate with an ever changing group of college students at the helm.
5) Message boards : News : New Poll Regarding GPU Application of N-Body (Message 74973)
Posted 1 day ago by Profilemikey
Post:
On top of not making a bit of sense to even have it around, what's the point if it's not as efficient as the current cpu app, they already have a gpu app here so don't NEED to release a slow inefficient one.


Of course to speed up n-Body processing they could offer the possibility to not "Run CPU versions of applications for which GPU versions are available" and credits similar to Separation would surely help too, right now when crunching n-Body one might get the impression, it isn't very valuable type of work considering the "pay" we get for it. ;-)


I agree the credits aren't up to par and several Admins have said they will look at it but they always come back 'we're happy where they are' which isn't helpful at all for those doing the actual crunching.
6) Message boards : Number crunching : Future of Milkyway@Home (Message 74965)
Posted 2 days ago by Profilemikey
Post:
Does anybody crunch Milkyway on their CPU?
Not me personally. Credits are too low.

It will be interesting to see how the credits pan out. I'd say the handful of big hitters skew these figures a bit.
I just know that from my point of view, future GPU's I buy will not perform as well at Milkyway@Home due to the DP gimping of consumer cards.

I was just curious what others though.


I personally have several pc's crunching MilkyWay cpu tasks, I crunch for wuprop which awards badges for the number of hours you put in not the credits a project gives you, so longer tasks are not always a bad thing. The pc's doing the cpu work are ones that really struggle to meet deadlines at other projects, they meet them but not always by a few days which is what I prefer. They are older dual quad core Intel Zeon cpu's that just crunch 24/7 15 tasks and a gpu task at a time but only at 2.?ghz. I also use it as a back-up project because they respect the zero resource share, ie only send me the tasks I need not hundreds as I wait for my main project to fill the cache again.
7) Message boards : Number crunching : Future of Milkyway@Home (Message 74963)
Posted 3 days ago by Profilemikey
Post:
That's why I wonder if this project will slowly produce less results.


Not really, the SP:DP ratio is maybe lower than it was before on some selected cards (4:1 IIRC only Cayman, Tahiti and Radeon VII), but on average the DP performance is still a lot higher than it used to be and CPUs are getting faster too. I don't see there any slowdown. Not sure what cards were released at the end of 2019, but that's when the last significant increase of monthly credit happened, you can clearly see it in the graph, quite stable since than with small after-christmas-bumps.


On top of that with all the new more than 16/24/32, without HT, core cpu's for pc's the trajectory should be nothing but upwards as their price comes down to affordable levels.
8) Message boards : News : New Poll Regarding GPU Application of N-Body (Message 74962)
Posted 3 days ago by Profilemikey
Post:
Releasing this application as is would slow down the overall throughput of the project.


Exactly the reason why N body application does not have a GPU version


On top of not making a bit of sense to even have it around, what's the point if it's not as efficient as the current cpu app, they already have a gpu app here so don't NEED to release a slow inefficient one.
9) Questions and Answers : Windows : ATI HD 4870 - Incorrect function. (0x1) (Message 74957)
Posted 3 days ago by Profilemikey
Post:
Hi,

my computer (Windows 10, FX-9590 and three ATI HD 4870 in crossfire) has problems with GPU work units. The work units start and need approximately three to four minutes to finish, but the result is a computation error. I tried to run a single work unit only and also disabled crossfire, but that didn't help.

Does anybody know why these errors are happening?


First crossfire is useless to Boinc as you cannot use multiple gpu's to crunch a single gpu task.
Second your gpu's are OPEN CL 1.0 and I think Milky?Way has a minimum of 2.0 right now.
10) Message boards : Number crunching : Future of Milkyway@Home (Message 74947)
Posted 4 days ago by Profilemikey
Post:
I'm just curious if anyone else has the same thoughts that I do around this project in the years to come. And by that I'm referring to newer GPU's.

For the first time in decades, I will have not 1 but 2 NVIDIA gpu's and as we all know..... they SUCK at Milkyway. I'll be losing an old stalwart in the old 280X which is probably capable of doing a few thousand less credits than a newer NVIDIA gpu I'm gussin.

Is it possible that Milkyway@Home could slow down in future if the best GPU's become project specific? Radeon VII's, Titans.
I find that NVIDIA cards finally do well on Einstein so for me personally, I gain on Primegrid & Einstein.

The point is, when I upgrade my cards as they get older, it doesn't look like the newer cards are doing so well with M@H due to the FP64 gimping.
Thoughts.

ps
I see the 7900XTX is still gimped 3.838 TFLOPS (1:16) vs a Radeon VII 3.360 TFLOPS (1:4)
For reference, my 3070Ti - FP64 (double) performance 339.8 GFLOPS (1:64) (urgh)


MOST people who crunch at Boinc Projects never read the forums at all, so if they have a problem they assume it's the Project and move on to a different one that hopefully works for them, that indicates the lack of willingness to tweak their pc's which leads to NO I don't think the AMD cards will ever not be here simply because they are a pain in the butt to make work in most Linux distros. Nvidia gpu's are MUCH easier to setup in Linux but in Windows they are the same as in Linux, download the drivers, install them, reboot the pc and you are gaming or crunching.

AMD gpu's can also pull their own weight and be cost effective too for gaming then if you add in the new Intel gpu's that are coming that also 'just work' in Windows pc's and MilkyWay and othrr Projects that benefit from the AMD cards have a good long run ahead of them. YES AMD is dropping the FP32/FP64 differences between them and Nvidia and it's no wonder Nvidia is doing better at some Projects right now. It turns out gaming doesn't benefit as much from the FP32/FP64 ratios as AMD thought.
11) Questions and Answers : Windows : Some tasks stalling (Message 74944)
Posted 6 days ago by Profilemikey
Post:
I was not aware that specific tasks could be limited. I had reduced my CPU access to 50% in BOINC, have now adjusted that up to 80% and will see how things run.

G


That's not what i meant, what I meant was do you have an app_config.xml file like this in your MilkyWay folder"

<app_config>

<app_version>
<app_name>milkyway_nbody</app_name>
<max_concurrent>1</max_concurrent>
<plan_class>mt</plan_class>
<avg_ncpus>2</avg_ncpus>
<cmdline>--nthreads 2</cmdline>
</app_version>
</app_config>

This particular file only uses 2 cpu cores per N-Body task AND only runs 1 task at a time.

Your problem could be that you are using all your cpu cores on a single tasks and your pc is locking up, which you could have just made worse with your change in settings, Link has better info on this than I do and IF it applies to you or not.

Link also probably has a better file than I do as I haven't run N-Body tasks for awhile as I'm doing Separation tasks right now.
12) Questions and Answers : Windows : Some tasks stalling (Message 74941)
Posted 6 days ago by Profilemikey
Post:
Thought the restart solved the issue, but no. Has run for 1.5 hours and now reporting 2.5 hours left. Like I said, it will just keep churning but never finish. So is there something about the Nbody tasks that is causing the issue on my hardware? (something not adequate to complete the task?). I am running a Dell machine, Windows 11 Pro (22H2), NVIDIA Model GeForce GTX 1660 Ti for graphics; i7 for processor and 16 GB RAM. Task id is de_nbody_11_14_2022_v182_40k__data__4_1666898646_819123. I have an older Win10 machine running also, and I see the same phenomena with an Nbody task showing running for days, but I don't think that is accurate. Many more of this type of task are in the list waiting to start, so I may have the same issue going on with all of them? I have an NVidia card on that machine also, is that possibly the common thread?

Just trying to understand the cause. Like I said, hate to abort the tasks.

G


Are you limiting the n-body tasks to X number of cpu cores or are you letting MilkyWay decide how many to use?
13) Message boards : Number crunching : seems AMD VII cannot be used on a riser (Message 74911)
Posted 18 days ago by Profilemikey
Post:
For what it's worth, I tried one of those ribbon cable risers that have all the x1 wiring, not just the wiring in the USB3 type cable.
Same problem: VII slowed down terribly. It needs to be in an x16 slot yet crypto miners run the VII on USB3 risers so I am unsure what is happening.
The eBayer I bought the card from was a crypto miner and had no problem as all the cards were in x1 USB3 risers and suggested a bad risers but I tried several.


A guy on Einstein was talking about using risers and said the key to the cabling is you need GOOD cabling not JUST cabling, he said just any cabling is flaky and will drop the signal all the time while the GOOD cabling will maintain the signal, I will try and ask him which is the GOOD stuff tonight and get back to you.
14) Questions and Answers : Windows : GPU in non-continuous operation. (Message 74908)
Posted 18 days ago by Profilemikey
Post:
For what it is worth, I updated the Milkyway fix "mod" using BOINC version 7.20.2
https://github.com/JStateson/Milkyway-7-21
If you are running 7.15.0 there is no Milkyway advantage other than having 7.20.2 functionality instead of 7.14
Any problems post as an issue over at github.


Per chance does your 'fix' include the Lunatics 'fix' for Einstein as well, or is yours solely focused on Milkyway?

Not sure what is broken at Einstein that needs a "fix" Mikey.

Can you elucidate the problem?


Poor choice of words, the speed-up would have been a better choice I think

I will try and compile Joseph's Linux BOINC client and drop it into the Lunatics AIO version of BOINC on a spare PC for beta testing his MW "fix"[/quotd]

WOO HOO!!

[quote]Only problem is all I have are Nvidia cards and he mentions they aren't fast enough to trigger the problem at MW.

But I used to run into the MW Scheduler problem all the time back when I was running MW at 100% resource share. Why I asked our dev to come up with the report_delay parameter for our Pandora client which he kindly put into the cs_scheduler.cpp for me even though I was the only team member running MW at 100% at that time.


Hmmmm that does present a problem
15) Questions and Answers : Windows : GPU in non-continuous operation. (Message 74906)
Posted 19 days ago by Profilemikey
Post:
For what it is worth, I updated the Milkyway fix "mod" using BOINC version 7.20.2
https://github.com/JStateson/Milkyway-7-21
If you are running 7.15.0 there is no Milkyway advantage other than having 7.20.2 functionality instead of 7.14
Any problems post as an issue over at github.


Per chance does your 'fix' include the Lunatics 'fix' for Einstein as well, or is yours solely focused on Milkyway?


That Einstein mod is in Linux and AFAICT makes an improvement in performance of Linux applications. There was also a mod to BOINC: 7.17 and 7.19

It was done by Petri and possibly others using Linux
This Einstein@home App (v1.0 by petri33) was built at: Apr 28 2022 18:47:15


All I have done is modify the scheduling algorithm in BOINC to bypass that 91 second delay that the Milkyway server wants.


And your mod works great!! Thank you!!
16) Questions and Answers : Windows : GPU in non-continuous operation. (Message 74903)
Posted 21 days ago by Profilemikey
Post:
For what it is worth, I updated the Milkyway fix "mod" using BOINC version 7.20.2
https://github.com/JStateson/Milkyway-7-21
If you are running 7.15.0 there is no Milkyway advantage other than having 7.20.2 functionality instead of 7.14
Any problems post as an issue over at github.


Per chance does your 'fix' include the Lunatics 'fix' for Einstein as well, or is yours solely focused on Milkyway?
17) Message boards : Number crunching : Inaccurate run times - de_nbody (Message 74902)
Posted 21 days ago by Profilemikey
Post:
In the end some 70+ jobs were cancelled due to the end date. Shame the jobs dident arrive with a more realistic run length. I know I could change the amount of work to store, but other projects get it about right...... usually.


They said the earlier tasks in a run take longer than the end of the run tasks, I think we are still in the early stages of this run. The run is a snapshot of an area they are looking to find something in, the early tasks have alot of 'stuff' to find so they take longer than the tasks at the end of the run where generally speaking there is little 'to see'.
18) Message boards : Number crunching : New Benchmark Thread - times wanted for any hardware, CPU or GPU, old or new! (Message 74898)
Posted 26 days ago by Profilemikey
Post:
Here are some more WU times.


BOINC Version: 7.4.36

BOINC Version: 7.4.36
.


You have some OLD versions of Boinc running there, I thought all the Projects stopped accepting tasks from any version below 7.10.? but obviously that was wrong. The latest release version of Boinc is 7.20.2.


Thanks for providing that info and especially the message url


Thank you for doing that, it was a totally useless message otherwise wasn't it!!
19) Message boards : Number crunching : New Benchmark Thread - times wanted for any hardware, CPU or GPU, old or new! (Message 74892)
Posted 27 days ago by Profilemikey
Post:
Here are some more WU times.


BOINC Version: 7.4.36

BOINC Version: 7.4.36
.


You have some OLD versions of Boinc running there, I thought all the Projects stopped accepting tasks from any version below 7.10.? but obviously that was wrong. The latest release version of Boinc is 7.20.2.
20) Message boards : News : Award Badges Going Live Soon! (Message 74891)
Posted 27 days ago by Profilemikey
Post:
test message


Looks good!!!


Next 20

©2023 Astroinformatics Group