Message boards :
Number crunching :
Processing both R9 & R10 tasks on the same machine
Message board moderation
Author | Message |
---|---|
Send message Joined: 23 Nov 17 Posts: 47 Credit: 27,378,777 RAC: 4 |
Since yesterday around 1 pm the Rakesearch server does not reliably deliver any R9 tasks to may machines anymore. As long as the app_info.xml of the optimized Rakesearch app is located in the project directory, none of the novel R10 tasks can be processed. In order to test whether the same machine can be used to process both, the old R9 tasks usind the optimized app and the new R10 tasks using the non-optimized original app, I did the followning test: I deleted the app_info.xml of the optimized app from the project directory and simply renamed the optimized app from rakesearch.exeto rakesearch_7.02_windows_x86_64.exe(which is the name of the original non-optimized app for R9 tasks). As a result, the machine now processes both, R9 tasks (using the re-named optimized app) and the novel R10 tasks (usign the original app). I applied these setting to exactly 14 test tasks of the R9 type. So far, two of these validated successfully (against clients with the original app): https://rake.boincfast.ru/rakesearch/workunit.php?wuid=24010823 https://rake.boincfast.ru/rakesearch/workunit.php?wuid=24010823 Of the remaining 12 tasks, 10 are sitting in the validation queue (status: pending) while two more are processing. It should be noted that the server records the returned results as processed with the original client (although in fact I used the optimized one). Because I do not know whether this client renaming procedure might cause any issues to the project I am unaware of, I limited this to 14 known tasks and have stopped receiving further R9 tasks on the test machine (computer ID: 3819) until someone of the project lead confirms that this approach is OK (I also have a full list of the tasks I used for testing). Michael. P.S.: It would be very nice, if an optimized client could be released which allows to process the novel R10 tasks because with the R9 tasks, the original client is rather slow and therefore requires significantly more electricity to yield results compared to the optimized one. President of Rechenkraft.net. Fördern, kooperieren und konstruieren statt fordern, konkurrieren und konsumieren. |
Send message Joined: 23 Nov 17 Posts: 47 Credit: 27,378,777 RAC: 4 |
I applied these setting to exactly 14 test tasks of the R9 type. So far, two of these validated successfully (against clients with the original app): Oh, my mistake - so far only vs. clients with the OPTIMIZED app. Now it's three successful validations. Michael. President of Rechenkraft.net. Fördern, kooperieren und konstruieren statt fordern, konkurrieren und konsumieren. |
Send message Joined: 8 Sep 17 Posts: 99 Credit: 402,603,726 RAC: 0 |
When you do it this way, replaced binary will be used until BOINC restart - after it BOINC will download official binary again. Note that official binary is not able to properly load checkpoint files from optimized app, so it will not work properly. If you want to use both apps, you need to add rank 10 app to app_info.xml. Do do this, you need to find appropriate tags for new app in your client_state.xml, and copy them to app_info.xml. Of course you will also need binaries for both apps. |
©2024 The searchers team, Karelian Research Center of the Russian Academy of Sciences