1) Message boards : Number crunching : No GPU work? (Message 37330)
Posted 11 hours ago by Toby Broom
There has never been GPU work.

I think the default BOINC config enables GPU work so when they update the server code it comes back, on the boinc.com page they removed it when I asked but now its back again so I imagine that page is automatically generated from reported configs.
2) Message boards : Sixtrack Application : No new WUs (Message 37298)
Posted 3 days ago by Toby Broom
It's not possible based on the science that is under study. If the beam is unstable then it will crash the particles into the wall and the WU is finished. It's sort of random which WU will last a long time. Also I think it not so interesting for the science to make a beam that lasts a very long time as the luminosity goes down as the number of particles in the beam is lower so they will dump the beams after a threshold.
3) Message boards : Number crunching : Too Many Total Results (Message 36815)
Posted 22 Sep 2018 by Toby Broom
Looks like the vm is going on and off, this isn't ideal for the VM based work units.

configure boinc to allow computer use all the time (no suspend options checked)

Lower the "use at most" if you want your computer to be more responsive
4) Message boards : Number crunching : Task(s) complete, but... (Message 36656)
Posted 6 Sep 2018 by Toby Broom
I would abort the long runner, sometimes these happen.

For the other it should go if you retry it.
5) Message boards : Sixtrack Application : No more sixtrack tasks? (Message 36653)
Posted 6 Sep 2018 by Toby Broom
Yes there was some SixTrack yesterday but they all went.

Theory is reliable for work, CMS has work but is light as it's mostly testing. LHCb has work
6) Message boards : ATLAS application : Download failures (Message 36545)
Posted 23 Aug 2018 by Toby Broom
I see the issue with sixtrack
7) Message boards : ATLAS application : 3-core task crunches slower than 2-core task - why so? (Message 36442)
Posted 15 Aug 2018 by Toby Broom
I think this is due to the extra shuffling the OS has to do it make the tasks a little slower each time, the ATLAS team tested it with there many core servers and saw the same. You are doing more work overall but each task gets a little less efficient. You gain some though when the tasks overlap as one can be prepping while the other is running for example.

For the credit I think you get more for less time so the more cores the longer it takes as its 3xthe time for a 3 core, therefore the more cores the lower the credit?

I run 1core on all my machine except one as there is a limit of 50WU at once and that machine has more than 50cores so if I choose the 2 core option I can get 100WU
8) Message boards : ATLAS application : VirtualBox 5.2 (Message 36385)
Posted 12 Aug 2018 by Toby Broom
Yes, I did both, I allow 100% of CPU usage so it's likely to do with that?
9) Message boards : Number crunching : Change Request for the Term "Max # CPUs" (Message 36359)
Posted 9 Aug 2018 by Toby Broom
It's the stock config from BOINC.

I think we discussed this a long time ago the purpose of a job to try and stop people computers being swamped with work, for example if you ran 8, 8core tasks on your computer then it would lockup either from ram usage or cpu usage. So the project can set the defaults to be 1job and 1core then people can dial it up from there.

BOINC does a poor job with this as we all think abouts tasks as this is what the UI shows in client. When the project submits the work it's called a job hence the naming.

Also for ATLAS, unlimited jobs/tasks is not actually unlimited jobs/tasks, so even more confusing.
10) Message boards : ATLAS application : VirtualBox 5.2 (Message 36346)
Posted 8 Aug 2018 by Toby Broom
Personally the 5.2.16 gives many unmanageable errors with ATLAS. The CMS, LHCb, Theory have no issues.

The 5.1.38 works well for all tasks.

I don't think others have computers that can run so many WU at once?
11) Message boards : Sixtrack Application : What tipe of simulation my computer doses? (Message 36321)
Posted 7 Aug 2018 by Toby Broom
How about this if your more of a physics person?


or this


Correct it simulates which particles will be lost depending on the magnetic fields

The VirtualBox tasks are running well for me, be aware ATLAS raised the ram requirement to 3.9GB for a single core task scaling from there.
12) Message boards : Number crunching : "Waiting for memory" - although enough RAM available (Message 36312)
Posted 7 Aug 2018 by Toby Broom
I my opinion it's the responsibility of the project team to set it correctly, not BOINC. Since it's configerable on a per job basis. I don't think BOINC knows for any WU not just Virtual ones. Maybe the required ram? as you said this isn't valid for VMs.

The limits on WU are also a project configuration topic too, since theory allows more than one WU if the 1 core setting is selected as you would expect.

You could run 3 six cores with 3 in the queue.
Core/WU	        WS MB	     BOINC Use	 GB         Running	 Queued
1	         3900	       3.8	             1	           0
2	         4800	       4.7           	     1	           0
3	         5700	       5.6	             3        	   0
4	         6600	       6.4	             4	           0
5	         7500	       7.3	             4	           1
6	         8400	       8.2	             3	           3
7	         9300	       9.1	             3	           4
8	        10200	      10.0	             3	           5
13) Message boards : Number crunching : "Waiting for memory" - although enough RAM available (Message 36288)
Posted 7 Aug 2018 by Toby Broom
The memory in app config is not known by boinc, boinc uses the working set defined by the project to calculate if it has enough free ram to start another task.

You can try to tune the number of cores on the web to match the working set in the appconfig or you can choose 1 core on the web and force more cores with appconfig. With the 2nd option now you have to be careful that boinc doesn't start too many tasks and over load the ram on your computer.

Since the project by default use 4800MB, you could stop using the appconfig and go with websettings, although the 2core will use 5700MB under new rules.
14) Message boards : CMS Application : no new WUs available (Message 36281)
Posted 6 Aug 2018 by Toby Broom
The CMS team said they have to totally overall the VM innards, so I assume there would be a whole load of errors, until they get it all worked out.
15) Message boards : Number crunching : fubar host of the day (Message 36211)
Posted 2 Aug 2018 by Toby Broom
Sorry, I read something over on the main boinc forums about issues with gridcoin and the use of account mangers in a non-standard manner.

Looks like I bade a bad assumption
16) Message boards : Number crunching : fubar host of the day (Message 36205)
Posted 2 Aug 2018 by Toby Broom
I'm think for gridcoin it because the users are automatically added to this project without really knowing so they don't realize they need virtualbox.
17) Message boards : Number crunching : Host won't download new tasks (Message 36204)
Posted 2 Aug 2018 by Toby Broom
I can defiantly not recommend 5.2.x for ATLAS, for the other project it looks OK.
18) Message boards : Number crunching : VirtualBox needed? (Message 36158)
Posted 1 Aug 2018 by Toby Broom
It's normal to have these left over files, they don't seem to cause any problems
19) Message boards : ATLAS application : Atlas tasks "Postponed: VM job unmanageable, restarting later." (Message 36153)
Posted 31 Jul 2018 by Toby Broom
I guess my previous actions were the best. As if we don't try and work around the issues and stop working for the project then they would address the request that we have.

I only run one core task on my machines as it the most efficient, I have one that run dual core as there is a limit on the number of tasks that you can run. compared to the other projects I don't contribute much to ATLAS as it's not possible to configure my computers to do more when shared with the other projects.

I expected it to work well as it was working well before so that set my expectations, hence the roll back.

If the task is postponed then in my experience it's never come back from that state, I think if you restart Boinc, then it will come back. The biggest problem with that state is it stops boinc from getting new tasks so when left un-managed it drains the queue
20) Message boards : Cafe LHC : Rewards (Message 36150)
Posted 31 Jul 2018 by Toby Broom

Treats from the project

Next 20

©2018 CERN