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: 22
Posts: 22   Pages: 3   [ Previous Page | 1 2 3 ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 2176 times and has 21 replies Next Thread
gomeyer
Senior Cruncher
USA
Joined: Jul 11, 2008
Post Count: 161
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Lock-up/Memory Problems

99% is 1% less from 100%... how useful is that ;? . . .

True enough, although this has never been an issue before. I think more to the point is that these WUs are simply using too much memory.
----------------------------------------

[Aug 21, 2013 1:09:38 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: Lock-up/Memory Problems

Well, I've hinted you [and any other reader] to what you can do to stop the freezing [during system in use] when the subjected molecule/compound simply demands a bigger model space, over which there's little control... automatically pause tasks/cores instead of you doing the manual core on / off switching. The very reason these client functions were implemented, so you don't have to manage hand on or get annoyed/frustrated/irritated, when choosing to crunch during system use and tasks falling over.

--//--
[Aug 21, 2013 1:18:17 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 22   Pages: 3   [ Previous Page | 1 2 3 ]
[ Jump to Last Post ]
Post new Thread