After running successfully on my Windows 10 PC with an AMD Ryzen 5 1400 CPU, I joined Rosetta@home also on my slowest CPU, an AMD E-450 running OpenSuSE Linux Leap 15.0. I hope it can meet the 3 days deadline.
Tullio

---

r@h tends to run quite well in linux, but i'd guess AMD E-450 is a laptop? some of the lessons learned running things on Pi4 are:
1) use a small to zero task cache setting e.g. download 0.1 days of work and 0 additional days.
2) memory may be a problem so if the notebook is not going to be used for other than boinc, you may like to set memory use as 100%
3) cooling in additional to memory may be a problem, one way with that is to limit the number of cpu cores used e.g. like 75% or 50%
that may help reduce the number of concurrently running threads and reduce the number of 'waiting for memory' incidences
and run cooler as well

It is a HP laptop, running 24/7 since 2014. I used it to run Einstein@home CPU tasks, but I abandoned that project since they told me that the GTX 1060 board on my Windows 10 PC with 3 GB Video RAM was not big enough. It is running GPUGRID tasks full blast. From what I saw via the "top" command the HP is running two tasks and a third one is waiting to run. I use the NNT command not to overload it.
Tullio

---

After running successfully on my Windows 10 PC with an AMD Ryzen 5 1400 CPU, I joined Rosetta@home also on my slowest CPU, an AMD E-450 running OpenSuSE Linux Leap 15.0. I hope it can meet the 3 days deadline.
Tullio

Hi Tullio,

There is a project preference called "Target CPU run time x hours" that I was told will help out a great deal. The default is 8 hours. I have mine set at 4 hours. Others here can explain what it does. Hope this helps. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Two Linux tasks completed, two running and one waiting. Times are comparable to those of the Windows tasks.
Tullio

---

Tullio, be aware that for Rosetta the time a work unit runs is chosen by you. The default is 8 hours. As mentioned below, you can change the default time shorter (or longer). Credits are based on how much 'stuff' your computer/CPU calculates within that time frame. So you will not see very much variation in run times. (Occasionally one will run a shorter time when some 'maximum' amount of decoys is reached, or it may run up to a certain time over your chosen time attempting to accomplish a minimum amount of decoys.) So the real comparison should be between average credits given for your chosen time-frame...and it should be an average; credits vary from WU to WU depending what was accomplished. I have attempted to follow the separate threads on how credits are given, but quite frankly don't understand the details behind the science. In general, the more science done during a given time for a given WU, the more credit.

I see Linux is getting less credits than Windows for a very similar running time. As I said elsewhere I don't give a damn about credits. The mechanism of credits varies from project to project, so it is impossible to compare results obtained in different projects. Credits obtained in GPU tasks are usually bigger than those in CPU tasks. I come from SETI@home where this issue is much discussed.
Tullio

---

I agree with you that credits don't mean much of anything on their own, especially comparing projects. The only point here (that I was not clear about) is that within Rosetta, it is about the only way to compare between CPUs, operating systems, etc.

It is interesting that you see less credits between Linux and Windows. One of my setups is a a dual boot Linux or Windows, and it definitely shows better credits when on Linux vs. Windows, and not only on Rosetta.

Happy crunching!

Well, my Windows credits are obtained on a PC with a Ryzen 5 1400 CPU, much faster than the E-450 of the HP laptop which runs SuSE Linux Leap 15.0. On the Windows host, with a 24 GB RAM, I have a Linux Virtual Machine running OpenSuSE Tumbleweed with a 5.6.12 kernel, often updated. But I have enlisted it in Science United, which gave me only 2 Rosetta tasks, besides 40000 and more Milkyway@home tasks, plus 4000 Asteroids@home tasks.This on the Windows PC, which I have retired from Science United. But the running times are equal on the Windows PC and the HP laptop.
Tullio

---

All Linux tasks uploading and downloading correctly, both in BOINC Manager and Science United, which just sent me a Rosetta@home task pn my Linux Virtual Machine.
Tullio

---

Well, my Windows credits are obtained on a PC with a Ryzen 5 1400 CPU, much faster than the E-450 of the HP laptop which runs SuSE Linux Leap 15.0

Important to note that runtime is nothing to do with credits. Runtime is just the time each task targets to run.

Within that time, the faster machine will complete more "decoys" than the slower machine. That's basically what your credits will be based on.

Different projects are different. Some things will be similar to what you're used to, while others will be the direct opposite. You can't rely on assumptions built up elsewhere at completely unrelated projects.

---