App installieren
How to install the app on iOS
Follow along with the video below to see how to install our site as a web app on your home screen.
Anmerkung: This feature may not be available in some browsers.
Du verwendest einen veralteten Browser. Es ist möglich, dass diese oder andere Websites nicht korrekt angezeigt werden.
Du solltest ein Upgrade durchführen oder ein alternativer Browser verwenden.
Du solltest ein Upgrade durchführen oder ein alternativer Browser verwenden.
Projektnews Rosetta@home: Largest proteins ever run on R@h coming soon.
- Ersteller P3D-Bot
- Erstellt am
P3D-Bot
Bot von P3D
In the quest for knowledge about COVID and other proteins, R@h is adapting to meet the challenge.
I wanted to try to help everyone be aware that the project is preparing some of the largest protein WUs even run on R@h. These will take much longer to run per model than smaller proteins. This is going to make "estimated runtime remaining" very difficult to show accurately. It will increase the likelihood of tasks running longer than your WU runtime preference, especially if you have a runtime preference that is less than the 8 hours default. To accommodate, the watchdog will be napping longer that he used to. Only ending WUs that have run more than 10 CPU hours longer than the runtime preference.
These long-running models are going to result in a high degree of variation in runtime between tasks. You might see one task granted nearly twice as much credit as another. That because it ran two models rather than one. Credit should generally be proportional to the amount of CPU time invested in the task.
This high variation in runtime is going to present a challenge for the BOINC Manager in deciding how much work it should be requesting. You can help the BOINC Manager avoid pulling down too much work if you adjust your preferences for how much work to store to be under a day.
Also, several of you have recently reported work units that have completed before their runtime preference. This is going to become more common with these long-running models as well. As an example if you have the default 8 hour runtime preference and the first model takes 5 hours to complete, then 5 hours is where it will stop and report back because a second model would exceed the preference. The Project Team prefers you leave the runtime preference unset, which presently results in 8 hour runtimes. But if these high variations in runtimes are presenting problems for you, I should point out that setting a longer runtime preference will generally result in more consistent completion times. Just beware that runtime preference changes are applied to your existing downloaded work units as well as new work requests. So I always suggest making changes only when you have settings for a small work cache, and to only change the runtime preference a couple of notches at a time, so the BOINC Manager has time to see WUs complete with the new runtimes. This helps it request the amount of work that matches your preferences.
The work units that were running very short models and ending when they reached 1,000 models (before their runtime preference), or other very round numbers, have been adjusted to allow a larger maximum number of models. This will help them fill out their runtime preference, using the additional time to compute more models. This will help runtimes of this type of work unit to be more consistent.
Weiterlesen auf der Projekthomepage
I wanted to try to help everyone be aware that the project is preparing some of the largest protein WUs even run on R@h. These will take much longer to run per model than smaller proteins. This is going to make "estimated runtime remaining" very difficult to show accurately. It will increase the likelihood of tasks running longer than your WU runtime preference, especially if you have a runtime preference that is less than the 8 hours default. To accommodate, the watchdog will be napping longer that he used to. Only ending WUs that have run more than 10 CPU hours longer than the runtime preference.
These long-running models are going to result in a high degree of variation in runtime between tasks. You might see one task granted nearly twice as much credit as another. That because it ran two models rather than one. Credit should generally be proportional to the amount of CPU time invested in the task.
This high variation in runtime is going to present a challenge for the BOINC Manager in deciding how much work it should be requesting. You can help the BOINC Manager avoid pulling down too much work if you adjust your preferences for how much work to store to be under a day.
Also, several of you have recently reported work units that have completed before their runtime preference. This is going to become more common with these long-running models as well. As an example if you have the default 8 hour runtime preference and the first model takes 5 hours to complete, then 5 hours is where it will stop and report back because a second model would exceed the preference. The Project Team prefers you leave the runtime preference unset, which presently results in 8 hour runtimes. But if these high variations in runtimes are presenting problems for you, I should point out that setting a longer runtime preference will generally result in more consistent completion times. Just beware that runtime preference changes are applied to your existing downloaded work units as well as new work requests. So I always suggest making changes only when you have settings for a small work cache, and to only change the runtime preference a couple of notches at a time, so the BOINC Manager has time to see WUs complete with the new runtimes. This helps it request the amount of work that matches your preferences.
The work units that were running very short models and ending when they reached 1,000 models (before their runtime preference), or other very round numbers, have been adjusted to allow a larger maximum number of models. This will help them fill out their runtime preference, using the additional time to compute more models. This will help runtimes of this type of work unit to be more consistent.
Weiterlesen auf der Projekthomepage
koschi
Grand Admiral Special
- Mitglied seit
- 11.11.2001
- Beiträge
- 5.760
- Renomée
- 732
- Standort
- 0511
- Mitglied der Planet 3DNow! Kavallerie!
- Aktuelle Projekte
- sieher Banner
- Lieblingsprojekt
- WCG, Einstein, Universe
- Meine Systeme
- R7 3900X @ 85W + 2 x Vega 56, 8 x Odroid C2, 8 x Odroid XU4, 4 x Odroid N2, 3 x Nvidia Jetson TK1
- BOINC-Statistiken
- Folding@Home-Statistiken
- Prozessor
- R9 3900X
- Mainboard
- Asus PRIME X370 PRO
- Kühlung
- Thermalright Le Grand Macho RT
- Speicher
- 2x32 GB DDR4 Corsair Vengeance LPX 3200@3200
- Grafikprozessor
- 2 x Sapphire Pulse Vega 56
- Display
- LG UltraFine 32UN880-B
- SSD
- Samsung EVO Plus 870 1TB & 850 500GB, Crucial MX500 1TB
- Optisches Laufwerk
- PIONEER BDR-209DBK
- Soundkarte
- Nubert nuPro A-20 (USB), Pioneer SE-MS7BT(K) (BT)
- Gehäuse
- Fractal Design Define R5 PCGH
- Netzteil
- BeQuiet! StraightPower 11 850W
- Betriebssystem
- Ubuntu LTS
- Internetanbindung
- ▼220 ▲40
https://boinc.bakerlab.org/rosetta/forum_thread.php?id=13826#94811
Die neuen WUs könnten bis zu 4GB RAM benötigen.
Sammelbestellung? :-D
Die neuen WUs könnten bis zu 4GB RAM benötigen.
Sammelbestellung? :-D
sompe
Grand Admiral Special
- Mitglied seit
- 09.02.2009
- Beiträge
- 14.450
- Renomée
- 2.011
- Mein Laptop
- Dell G5 15 SE 5505 Eclipse Black
- Prozessor
- AMD Ryzen 9 3950X
- Mainboard
- MSI MPG X570 GAMING PRO CARBON WIFI
- Kühlung
- Wasserkühlung
- Speicher
- 4x 16 GB G.Skill Trident Z RGB, DDR4-3200, CL14
- Grafikprozessor
- AMD Radeon RX 6900 XT
- Display
- 1x 32" LG 32UD89-W + 1x 24" Dell Ultrasharp 2405FPW
- SSD
- Samsung SSD 980 PRO 1TB, Crucial MX500 500GB, Intel 600p 512GB, Intel 600p 1TB
- HDD
- Western Digital WD Red 2 & 3TB
- Optisches Laufwerk
- LG GGC-H20L
- Soundkarte
- onboard
- Gehäuse
- Thermaltake Armor
- Netzteil
- be quiet! Dark Power Pro 11 1000W
- Betriebssystem
- Windows 10 Professional, Windows 7 Professional 64 Bit, Ubuntu 20.04 LTS
- Webbrowser
- Firefox
Na dann hoffe ich mal das ich nicht allso viele aufeinmal davon bekomme. ^^
Zuletzt bearbeitet:
Rekrut
Admiral Special
- Mitglied seit
- 26.06.2006
- Beiträge
- 1.978
- Renomée
- 27
- Mitglied der Planet 3DNow! Kavallerie!
- Aktuelle Projekte
- Asteroids, Milkyway, Yoyo
- Lieblingsprojekt
- WCG
- Meine Systeme
- 2x AMD Ryzen 9 3950X, 1x AMD Radeon 7900 XTX, 1x NVIDIA RTX 4070 TI
- BOINC-Statistiken
- Folding@Home-Statistiken
- Prozessor
- AMD Ryzen 9 3950X
- Mainboard
- Asus PRIME B450M-A
- Kühlung
- Noctua NH-U12S SE
- Speicher
- 4x 16 GB HyperX FURY DDR4 2667MHz
- Grafikprozessor
- AMD RADEON 7900 XTX
- Display
- LG 4K IPS
- HDD
- 1x 1 TB HDD 2,5 Zoll 10.000 U/min.
- Optisches Laufwerk
- Nicht vorhanden
- Soundkarte
- Asus Xonar II
- Gehäuse
- be quiet! DARK BASE 700, Tower-Gehäuse
- Netzteil
- be quiet! Dark Power 12 750W
- Betriebssystem
- Windows 10
- Webbrowser
- Firefox
Ich kann die Zeiten in den Einstellungen diesmal sehr hoch stellen, schaut mal bei euch, sieht interessant aus, bald kann Rosetta sich bei CPDN von den Laufzeiten her anschließen Ist ja echt wahnsinn bei denen was die Ressourcen und Berechnungszeit angeht, die man nutzen kann.
Ähnliche Themen
- Antworten
- 0
- Aufrufe
- 190
- Antworten
- 2
- Aufrufe
- 252
- Antworten
- 1
- Aufrufe
- 259
- Antworten
- 0
- Aufrufe
- 141
- Antworten
- 0
- Aufrufe
- 232