Where is the setting to change the long term debt window?

If I understand what your asking set :-

<rec_half_life_days>X</rec_half_life_days>

to 1 in cc_config.xml

Thanks, it appears to be set to 10 already so perhaps I changed this years ago and forgot.

I was asking about what Mikey referred to a few posts earlier.

Where is the setting to change the long term debt window?

I realize that the project has no work right now, but when I update it to see if that has changed, the response I get is this


4/13/2025 4:51:16 PM | SiDock@home | Not requesting tasks: don't need (CPU: ; NVIDIA GPU: no applications)


Not needed is blatantly false

I have five projects with the same resource share, SIDOCK among them

SIDOCK's recent work ranges from 5 to 12% of the other four The other four continue to download and run WUs


Why am I being told that work is not needed?

The queue is exhausted at this moment.

Hi Greg! Because these were the last tasks. There won't be any new ones for a while.

Hey Hoarfrost...define "awhile" in terms of time if you can.
Weeks or months?

Can something please be done to fix the server? It is damn slow just trying to move around on the web pages. But that is not the worst problem. Tasks take multiple attempts to upload. This is not an occasional thing. It is a constant problem.

What needs to be done to address this?

I got an automatic notice that says "SiDock@home: Notice from server
CurieMarieDock 0.2.0 long tasks needs 53.85MB more disk space. You currently have 74.15 MB available and it needs 128.00 MB,.
" want to know how to resolve this, and get my pc crunching again?

Before I asked, I looked through the options and did not see anything I could do. Help.

Hi folks! Greg, thank you for message.

We have started creating new tasks for x86, for target # 11, "corona_Sprot_delta_v1", in parallel to ARM-tasks. They will be relatively short and the queue of tasks may be exhausted sometimes.

Good luck!

All of the tasks available at the moment are for ARM based machines.

Even my ARM based machines don´t get any work units.

It seems that for the last few days there have been no work units available at all. All my machines are idle as far as BOINC goes. What's up with that?

Please do like the BOINC projects "Amicable numbers" and "RakeSearch", and add a "percentage completed" line to the server status page, either for the whole project, or for each application, as well as a completion estimate (year and month), based on the current speed.

Note that the <max_concurrent> tag in the app_config.xml file sets the maximum number of tasks of a specific application to run at a given time. It does not control the work cache size, meaning if you set the max_concurrent to "2" say, it will download tasks to fill whatever cache size and the cpu thread to use that you specified. It will only run 2 tasks irrespective of your cache size. However there is a bug in the boinc manager (not sure what version that is) that could potentially load more tasks that you need and override the cache size. Just fyi.

The bug has been fixed in the latest versions of the Boinc Client. Even before that, I have been running max_concurrent with a small cache size for several years without a problem - each project (including SiDock and CPDN) working according to their project weighting. (If anything it’s WCG that overfills the cache with respect to its project weighting).

Hi Bryn

Yeah i use BOINC 8.0.0 already, so you say that if I set <max_concurrent>1</max_concurrent> will only request 1 task from server ?

I only will be able to try this in few days or so cause I need to crunch multiple SiDock tasks that i already got ..

Thank you

Note that the <max_concurrent> tag in the app_config.xml file sets the maximum number of tasks of a specific application to run at a given time. It does not control the work cache size, meaning if you set the max_concurrent to "2" say, it will download tasks to fill whatever cache size and the cpu thread to use that you specified. It will only run 2 tasks irrespective of your cache size. However there is a bug in the boinc manager (not sure what version that is) that could potentially load more tasks that you need and override the cache size. Just fyi.

Thank you for reply @pututu. Let me clarify

Besides Sidock, I crunch multiple projects (wcg, rosetta etc) which may have tasks outage periods, that is why i keep setting to cache work for ~1 day

Computer has 8 CPUs and about 40-60 various tasks in the queue, and usually with these projects, the task deadlines are quite short, for example 3 days with Rosetta. Sidock has about 6 days to deadline

Other projects crunch a task in about 1-3 hours, while Sidock crunches in about 2 days

Computer is 80% turned on.

So, when Boinc client requests Sidock, computer usually gets 8 tasks and this immediately puts all tasks at risk cause instead of 1 day cache it now has ~3 days cache and this causes Boinc to juggle the tasks

It would be more convenient to set a limit to avoid such issue

Hello Bryn!

There have been no changes in recent weeks (or even months). Looks like credit "arranging" due computing stats gathering and counting.

Hello Natalia, hello hoarfrost. I am reaching 25.000 hours

25,000

The WUs that are running should complete soon and I’ll confirm when they do.

This is good news! Thank you for notice!

The next 6 WUs have all finished clean in just over 24 hours with several more about to finish. Happy days :-)

WOO HOO!!! You may have just solved a problem since the beginning of Boinc!! I sure hope so anyway!!! You should get that adde4d to the Wiki page of Boinc errors.

The WUs that are running should complete soon and I’ll confirm when they do.

This is good news! Thank you for notice!