Where is Rosetta's working directory, please? The BOINC-manager log doesn't show it. I need to move all BOINC work off the nvme drive.

I need to move all BOINC work off the nvme drive.

Why?
Unless you plan to muck around with Symlinks or a Hard link etc, set No New Tasks, finish what you have, uninstall BOINC & reinstall it to a different default drive.

---

Grant
Darwin NT

So, you don't know it's working directory?

Upstream documentation:
https://boinc.berkeley.edu/wiki/BOINC_Data_directory

On Linux, it is usually /var/lib/boinc or /var/lib/boinc-client.

Edit — if you run boinc as a service, refer to the documentation of your Linux distribution to learn where the service is configured. For example, in Linux Mint 18.3, the boinc-client data directory is configured in /etc/default/boinc-client. You may change it there while the boinc-client service is not running.

So, you don't know it's working directory?

Nope.
But Google came up with this.

Still curious as to why the need to move.

---

Grant
Darwin NT

Presumably, the nvme drive can only handle so many writes in it's lifetime. So, move to a drive that doesn't have those physical issues.

---

Rosetta Moderator: Mod.Sense

Presumably, the nvme drive can only handle so many writes in it's lifetime. So, move to a drive that doesn't have those physical issues.

Possibly, which is a rather silly reason to move it.
Even though Rosetta does hammer the disk compared to other projects (and other workloads), the fact is the total amount of writes it does is bugger all of what the drive is capable of dealing with before it eventually dies, in 20 or more years time with much, much heavier use than even Rosetta does with it.
And even then, as Annandtech showed many years ago, even consumer based SSDs will outlast their specified life expectancy, often by a huge margin. It took them 18 months to kill the last of their consumer SSDs, using loads that far exceed any regular desktop's extreme disk usage (yes they were SLC drives, and more recent flash technologies (MLC, TLC & QLC) have less total writes before they will fail. But the software to reduce write amplification, combined with capacities much larger than the tasted drives, means current SSD would probably last longer, even with a heavier load).
The SSD Endurance Experiment

---

Grant
Darwin NT

@Grant (SSSF),
potential reasons to move some or all content of the boinc data directory are very similar to potential reasons to move the operating system, application program applications, data from work or education, or data from spare time activities.

In other words, imagine somebody asked where to find their collection of vacation photos. Would your immediate response be "Why?" too?

The boinc data directory holds client state. There may be various reasons to preserve client state over hardware changes, or just changes to the allocation of hardware resources. Similar to that there are various reasons to preserve client state over a power off/on cycle of the host.

Followed the links, read the descriptions.
Still don't know where Rosetta hides it's working directory.
Debian Linux, Buster (10), 64-bit

In other words, imagine somebody asked where to find their collection of vacation photos. Would your immediate response be "Why?" too?

Nope. But that is very different to the opening post.
If they had asked "where to find their collection of vacation photos. I need to move all vacation photos off of the nvme drive" then It would have been why.

The boinc data directory holds client state. There may be various reasons to preserve client state over hardware changes, or just changes to the allocation of hardware resources. Similar to that there are various reasons to preserve client state over a power off/on cycle of the host.

And they could have answered that.
I would rather help someone, if possible, than just let them go ahead and do something completely unnecessary & pointless and waste all that time and effort for no benefit.
But without a response, there's no way of knowing if there really was a need to move the installation or not.

---

Grant
Darwin NT

Grant, help, don't help.
It's not up to you to decide how I configure my systems.
Thank you for playing.

Grant, help, don't help.

And knowing why people do things makes it easier to help, now and in the future.
*shrug*

---

Grant
Darwin NT

Followed the links, read the descriptions.
Still don't know where Rosetta hides it's working directory.
Debian Linux, Buster (10), 64-bit

BOINC under Debian uses /var/lib/boinc-client. Under that there is a projects folder and then one for each project you’ve signed up to. However when BOINC is running a task it will use the slots folder and allocate a folder under there for each running task. There is no project specific working directory. That is you’ll end up with as many slot folders as you run tasks at the same time. The slot folders are cleaned up as each task finishes.

For what it’s worth all my number crunchers have NVMe drives as their local storage. I have set the checkpoint interval in BOINC to 300 seconds for them as well as keeping apps in memory, my i7-8700’s have 32GB of memory.

---

BOINC blog