Skip to content
Prev 14395 / 15075 Next

macOS may not give R much time in a long compute

On 2/18/23 6:40 AM, Prof Brian Ripley wrote:
I'm "using the newest version of RStudio" [Version 2022.12.0+353 
(2022.12.0+353)].  This means I am running R.app?
Thanks for the term "app nap" and the reference to ?4.1 of the 
R-admin manual.  I had not previously heard of "app nap", but that 
sounds like what I've encountered, and that section of the manual 
suggests that if I encounter this problem again, I can open a terminal 
and enter:


defaults write org.R-project.R NSAppSleepDisabled -bool YES


	  Will it take effect immediately?  Or will I need to restart R?


	  I've changed the code since I reported this problem, and I have not 
encountered this problem since.  I'm not sure, but when I noticed this 
problem, I may have had "if(max(et3i)>1800)" [progress report every 30 
minutes] instead of "if(max(et3i)>180)" [progress report every 3 
minutes].[*]  With luck, this change may fix this problem.  If yes, 
might you have any idea what the threshold might be?


	  Thanks very much.
	  Spencer Graves


[*] I'm not sure what threshold I was using when I encountered this 
problem:  180 or 1800 seconds.  I foolishly didn't save the output that 
included lines like the following:


iscan =  22992 ; et3i =  180 26 104


iscan =  32124 ; et3i =  22 1 180