Hi guys,

i've joined two projects: Rosetta@Home and LHC@Home, the project tabs show me allocation of resources is 50% for every project.

Both projects are enabled but in activity tab LHC@Home run as he ave priority on Rosetta@Home...

L@H run a WorkUnit for 8cpus and stop all other tasks.

I did a test: this night i left the computer running only Rosetta tasks disabling LHC, this morning i enabled LHC and instantly it stopped all tasks and resumed an 8cpus task left incomplete yesterday...

It's possibile to have both projects running ?

PS The 8cpus tasks are a virtual box machine runned headlesses by boinc

My config:

BOINC client version 7.17.0 for x86_64-pc-linux-gnu
OpenCL CPU: Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (OpenCL driver vendor: Intel(R) Corporation, driver version 18.1.0.0920, device version OpenCL 2.1 (Build 0))
No usable GPUs found
libc: Debian GLIBC 2.30-4 version 2.30

Processor: 8 GenuineIntel Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz [Family 6 Model 60 Stepping 3]
Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm invpcid_single kaiser tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm ida arat pln pts

OS: Linux Debian: Debian GNU/Linux bullseye/sid [4.9.0-7-amd64|libc 2.30 (Debian GLIBC 2.30-4)]

Memory: 15.11 GB physical, 29.80 GB virtual

Disk: 45.58 GB total, 13.60 GB free

VirtualBox version: 6.1.4r136177

If left alone, the resource allocation will even out the time between your projects but this can be affected by things like tasks with very short deadlines get prioritised. It often takes a period of days or even weeks depending on project mix for resource share to be seen to be working.

Your CPU only has 8 threads.

You can limit each project to how much CPU cores it can access at any given time in app_config.xml. (eg: limit to 4 per project).

That can be done for projects which send their executables direct to your computer for native execution. Remember to set the --nthreads command line as well.

But I hesitated from offering that advice in this case because the project is LHC. They have the added abstraction layer of sending a virtual machine image, and then running their multi-threaded science application inside that. It's not as simple as you make it sound.

Your CPU only has 8 threads.

You can limit each project to how much CPU cores it can access at any given time in app_config.xml. (eg: limit to 4 per project).

The problem with that approach is if either of the projects runs out of WUs to send (Rosetta?) then the other project cannot take up the slack and you run half the machine empty.

Give it time and it will sort itself out.

One thing I have done is reduce the number of days it integrates the workload over from ?10? to 2 so that it gets back onto an even keel more quickly.