Development for LHC@home

See this post for details.

---

Okay, I will bring in more machines from my Network (I will have to slow down my Atlas *snief*)

Could you open for a second WU per Computer ?

Make sure theres plenty of cmsRun jobs in the queue...

ican't get any work

ican't get any work

There are 450 jobs in the queue at the moment; are you still dry?

---

Okay, I will bring in more machines from my Network (I will have to slow down my Atlas *snief*)

Could you open for a second WU per Computer ?

That's a question for Laurence, I feel; I may have the privileges to do it but I wouldn't know where.

---

ican't get any work

Your PC has only 3GB Memory this may be to low

And not shure if CMS can run on an 32 BIT-System

ican't get any work

Your PC has only 3GB Memory this may be to low

And not shure if CMS can run on an 32 BIT-System

CMS only offer 64-bit versions for automatic download, but I managed to get it running on a 32-bit machine (with a virtualisation-supporting CPU) by downloading the 32-bit version of the BOINC wrapper and running it through an app_info.xml file.

Interesting experiment, but hardly worth it in the long term.

I will try to update to an 64 bit OS then. Also, this way it will see all the 4GB RAM intalled

I will try to update to an 64 bit OS then. Also, this way it will see all the 4GB RAM intalled

Good idea, but, before you do this, check first if your BIOS has a VT-X Entry that you can enable.

I couldn't check this with CMS, but Atlas only works when VT-X is switched on.

Does anyone no more about CMS and VT-X ?

I will try to update to an 64 bit OS then. Also, this way it will see all the 4GB RAM intalled

Good idea, but, before you do this, check first if your BIOS has a VT-X Entry that you can enable.

I couldn't check this with CMS, but Atlas only works when VT-X is switched on.

Does anyone no more about CMS and VT-X ?

I'm reasonably sure that that is required.

---

Filipe's CPU (i3-4130) does have VT-x which may need turning on in the BIOS but it does not have VT-d that is used for Directed I/O.
I think VT-d may just speed things up for the VM but, like everybody else says, I'm not sure !

I have no doubt that this will be a successful test for CMS since ATLAS tested BOINC results for months before accepting BOINC as part of their regular production team.

Okay, I will bring in more machines from my Network (I will have to slow down my Atlas *snief*)

Could you open for a second WU per Computer ?

That's a question for Laurence, I feel; I may have the privileges to do it but I wouldn't know where.

More than happy to have the limit raised but if you are going to increase it I would advise letting people know in advance so that they can plan for it.

As it has always been a single WU since I started running it I haven't gone round and created app_config.xml files to limit it (though I probably will now). Others may not be reading the forum so may welcome as much notice as possible.

Might be too early for your actual testing, tomorrow, but it's working as described in the Seti post on:

Windows 10 Home, (upgraded from Win 7 so has Remote Desktop. A clean install of Win 10 Home won't have that, only in Pro)
Vbox 5.0.2 with corresponding Extension Pack and
Boinc 7.6.6

I upgraded from 8.1, that had RDP. The Home edition has not.
Tullio

Ivan, when will you start the challenge (or did you already ?)

By the way, I think, it is a little bit early for this challenge; the efficiency of the VMs is not as good as they should be:



As you can see in this graphic, machine AHuW74 and AHuW75 are 33% of their time idle. Atlas1 not much better.

Atlas4 and Atlas5 are doing fine; I think more than this 94% are not to reach

Ivan, when will you start the challenge (or did you already ?)

By the way, I think, it is a little bit early for this challenge; the efficiency of the VMs is not as good as they should be:



As you can see in this graphic, machine AHuW74 and AHuW75 are 33% of their time idle. Atlas1 not much better.

Atlas4 and Atlas5 are doing fine; I think more than this 94% are not to reach

I haven't yet, will probably have to postpone it a few days. Some issues have come up, as you know, and I haven't had time to get a suitably powerful yet non-data-intensive workflow cobbled together (there's a two-stage one that I might be able to join together).

---