I installed the debian package for it.
Which starts boinc automatically at boot.

My question is tho, in my processes monitor, i see that there are 4 different rosseta WUs. only one is running tho, but the other just take up memory (about 150 each). but when i look at the total memory being used, i'm only using about 350 (with all my apps running, music, firefox...etc.)

So that got me confused. Im rather new to the BOINC-Linux thing.
So any knowledge would be helpful :D
Thanks!

---

It sounds like you have set your preferences to leave tasks in memory while suspended (which is recommended, as it preserves the most work done). This settings says "in memory" but it really means virtual memory.

So, it sounds like your machine is running in to "waiting for memory". So it starts a task, finds it grows to need more memory then you are allowing for BOINC, then it suspends it, and begins another task in hopes that it will run in less memory.

So that is how you probably got 4 R@h tasks started at the same time. If you read the other active threads on the crunching board, many pertain to unusually large memory used by recently released tasks. And Rhiju has pulled these off the work queue until the memory utilization can be brought down with some further programming enhancements.

---

Rosetta Moderator: Mod.Sense

My question is tho, in my processes monitor, i see that there are 4 different rosseta WUs. only one is running tho, but the other just take up memory (about 150 each). but when i look at the total memory being used, i'm only using about 350 (with all my apps running, music, firefox...etc.)

That's how multi-threaded applications look like in Linux. While some OSes hide threads under one process ID, Linux exposes them. As they are not separate processes but rather one process run in several threads, there's only one set of memory being used. If you observe those processes closely, you'll notice that memory consumption is exactly the same for all of them. Additionally, they usually have sequential process IDs.
Number of processes can vary from one application to another. I've once built a SETI@home binary myself and instructed C compiler (I used Intel's CC) to create multi-threaded application. When running, it generally started anything between 2 and 5 threads. Most of CPU time was spent in one thread, but others also collected some (less than 1% though).

In short: nothing to worry about.

---

Metod ...