Use Rosetta on the one that has the most memory.2 boinc instances is easiest on 2 separate hosts. Just setup another PC for LHC
Based on StefanR5R's explanation I'm currently testing this on my main rig. I chose WCG as the second project. My goal is to, and I assume that your goal is pretty much the same, keep the lion share of the host's resources for Rosetta, but give the second project a little room to breathe. However, the scheduler will try to bring the second project up to speed, and therefore will prefer it for a (long) while. Now knowing, that the scheduler is trying to achieve the resource share over the long term, based on recent estimated credit, and taking into account that Rosetta has been the one and only project on this host, I set a very low value (1%) for the WCG resource share (in the device settings on the WCG site), and a very high one (99%) for Rosetta (in the project settings on the Rosetta site). With this 99:1 ratio, my host is still running mostly Rosetta tasks, but will occasionally insert or continue to work on a few WCG tasks. Overnight, it completed 17 WCG tasks (which are short with ca. 2h each, compared to the Rosetta standard tasks with 8h). Now comparing my overnight Rosetta output with the usual output verifies that it hasn't been reduced too much. I'll be further looking into this over the next few days or even weeks, and try to find out what resource share will give me the best short term credit distribution.Oh I see, what a daft system! I wish it would focus more on what's currently being crunched, any idea how long it would take to stabilise?
Atm I've turned the tap off for LHC in disgust, but if it's getting close to levelling out I could turn it back on again without Rosetta being totally excluded!?
Yeah, it is not that I'd like it in particular, but I can arrange myself with it I would also prefer an explicit core/thread based distribution option, but as I'm not a developer of that application, I'll take it as-is, as long as it works.I still think it's a daft system , they should at least give the option of thread division rather than RAC, i would think it would take several weeks for that to settle down?
Oh boy, you really have like a winning streak recently? Did you see where the "flash" originated? Otherwise, it is hard to say what might have died (or was severely wounded), without physical examination, i.e. opening the case and inspecting the electronics. In case the laptop works normally, it might have been the charger, but that's just a guess of course.On a separate note, I've just been distracted by a very loud pop and a flash from my laptop which was on charge!! No smoke came from it, the battery pack is cool and so was the charger (which it's power LED stayed on for several seconds as usual after I pulled the mains power), but their was definitely a smell of burnt electrics!
I quickly tried starting the laptop and it booted up just fine! lol (only let it run to the post screen as I need it for diagnostics on my car tomorrow, and don't want to drain the battery if I can't charge it anymore).
I don't get it, would could have blown?? m/brd cap??
Any news on the laptop? Is it still working normally? Maybe have a look at the hardware maintenance manual to check what's in that back right area without disassembling the unit (I have no idea what model you have). But I'd say it may not be a bad idea to preventively back up the data on it, just in case.Bit hard to say as it was in the corner of my eye, but it seemed to come from the back right of the laptop, the charger was at the front left of it, the charging port at the back left.
Be cautious with this. If both client instances happen to have the same CPID (cross project identifier), then take care that only one of the instances talks to a given project server. Safer is to have a unique CPID in each instance.a little messing with the client_state.xml
Or we could put a copy at teamanandtech.org.Maybe this could be a sticky so it can easier be found for new members?
Seems to work just fine! lolAny news on the laptop? Is it still working normally? Maybe have a look at the hardware maintenance manual to check what's in that back right area without disassembling the unit (I have no idea what model you have). But I'd say it may not be a bad idea to preventively back up the data on it, just in case.
|Thread starter||Similar threads||Forum||Replies||Date|
|Weekly DC Stats - 18APR2021||Distributed Computing||7|
|Weekly DC Stats - 11APR2020||Distributed Computing||36|
|Weekly DC Stats - 04APR2021||Distributed Computing||17|
|Weekly stats for 28MAR2021||Distributed Computing||21|
|Weekly DC Stats - 21MAR2021||Distributed Computing||14|