Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 49
Posts: 49   Pages: 5   [ Previous Page | 1 2 3 4 5 ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 55681 times and has 48 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Known Issue with Linux stuck workunits

armstrdj ,
Is that a fix for the memory issue or the Linux one , or both ? biggrin
(sorry , I couldn't resist) wink
It seems this thread got away from the original "Issue with Linux stuck workunits" question and started into talk about memory requirements.

By the way , Thanks for the update !
My Linux machines are eagerly waiting lots of Beta's to chew on.
----------------------------------------
[Edit 3 times, last edit by Former Member at May 2, 2012 3:20:07 PM]
[May 2, 2012 2:22:53 PM]   Link   Report threatening or abusive post: please login first  Go to top 
armstrdj
Former World Community Grid Tech
Joined: Oct 21, 2004
Post Count: 695
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Known Issue with Linux stuck workunits

It is only for the hanging workunits when multiple ones are running, the memory footprint is the same.

Thanks,
armstrdj
[May 2, 2012 5:04:33 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Known Issue with Linux stuck workunits

We are currently testing a fix in our Alpha testing environment. If things go well, so far so good, I would expect a Beta in the next couple of days. Thanks for everyone's patience while we work through this issue.

Thanks,
armstrdj

Outstanding!! Looking forward to the beta tests and ultimate production WU's

Thanks for the update armstrdj
Edit: referenced correct quote.
----------------------------------------
[Edit 1 times, last edit by Former Member at May 2, 2012 9:47:36 PM]
[May 2, 2012 9:44:02 PM]   Link   Report threatening or abusive post: please login first  Go to top 
uplinger
Former World Community Grid Tech
Joined: May 23, 2005
Post Count: 3952
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Known Issue with Linux stuck workunits

This issue is going to be considered closed, we have released the new version for linux to the grid that has a fix for this issue. The beta test went well. On Linux your version number for this application will be 6.09.

Thanks,
-Uplinger
[May 10, 2012 8:26:57 PM]   Link   Report threatening or abusive post: please login first  Go to top 
uplinger
Former World Community Grid Tech
Joined: May 23, 2005
Post Count: 3952
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Known Issue with Linux stuck workunits

I forgot to mention, we will be removing the linux 1 per host limitation. This will be done shortly, please be patient while we remove the limitation.

Thanks,
-Uplinger
[May 10, 2012 8:30:03 PM]   Link   Report threatening or abusive post: please login first  Go to top 
knreed
Former World Community Grid Tech
Joined: Nov 8, 2004
Post Count: 4504
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Known Issue with Linux stuck workunits

The limit has been removed.
[May 11, 2012 2:30:08 AM]   Link   Report threatening or abusive post: please login first  Go to top 
alver
Senior Cruncher
Joined: Nov 30, 2007
Post Count: 245
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Known Issue with Linux stuck workunits

Thanks for the updates. I had one stuck on one of my boxes, which I've just aborted, but that was from BEFORE this fix - I was about to remove the project from my list (I'm nearly 100% Linux), but instead I'll leave it running and let you know if I see any problems.

Thanks again.
----------------------------------------


(previously known as 'proxima' on SETI, UD, distributed folding, FaD, and Rosetta)
----------------------------------------
[Edit 1 times, last edit by alver at May 11, 2012 9:15:49 AM]
[May 11, 2012 9:10:37 AM]   Link   Report threatening or abusive post: please login first  Go to top 
kateiacy
Veteran Cruncher
USA
Joined: Jan 23, 2010
Post Count: 1027
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Known Issue with Linux stuck workunits

Excellent! I had noticed that I had received a second CFSW WU on a machine that already had one -- very nice!

Is it possible to explain in a brief way how the earlier WUs were able to interfere with one another? Just curious.
----------------------------------------

[May 11, 2012 12:38:55 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Known Issue with Linux stuck workunits

With this release now having run all core concurrent for about 48 hours on a dual boot quad, I'd say the CPU time on Linux is now very close to the W7-64 version (4.46 hours mean), but still a tad slower... 6-10 minutes (4.62 hours mean). Given the efficiency on a ''left alone'' system (99.65%), about 0.2% in favor of W7-64 (99.85%), for idle running, W7-64 is my choice to run this science in a "run exclusive" setup (Q6600).

For those who run their devices in "MM - last squeeze" mode.

--//--

P.S. The Llnux 11.10 was upgraded using the boinc/testing ppa from 6.12.33 to 7.0.27 dbfg-1. Installed smooth, asked if wanting to retain [customized] cc_config.xml, and after stop / start of daemon, no complaints so far.
[May 13, 2012 7:59:09 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 49   Pages: 5   [ Previous Page | 1 2 3 4 5 ]
[ Jump to Last Post ]
Post new Thread