Wow, you can find almost any explanation on the Internets. That doesn't mean
you should believe all of them. R does not do anything likely to tweak
interrupts... if that is your problem then you need to be on an
operating-system/computer-model-specific forum rather than this OS-agnostic
It is far more likely that your overall memory usage conditions have changed
since the last time you ran it... or that you didn't actually record all of the
things you did last time in your script. (Newbie R users often do things at the
console without putting them in their scripts.)
I suggest that you run your script one statement at a time and see where your
problem is. You might also want to make sure that other programs are not using
up a lot of your memory (which could involve some OS-specific tools or just
shutting down some other programs.)
On June 12, 2018 7:36:40 PM HST, akshay kulkarni <akshay...@hotmail.com> wrote:
>I ran a function in R three days ago and the execution time was about
>4 minutes. I ran the same function yesterday and the execution time was
>more than 6:50 minutes(I aborted the function after that time).
>I read in the Internet that this is possible. I also came to know that
>software or hardware interrupts are the main reasons.
>How do you know whether the delay was caused by interrupts? Which
>hardware or software triggered the interrupts? In general, how to know
>the exact cause of the delay in execution in R? Are there any packages
>for these analyses?
>Very many thanks for your time and effort....
>AKSHAY M KULKARNI
> [[alternative HTML version deleted]]
>Rfirstname.lastname@example.org mailing list -- To UNSUBSCRIBE and more, see
>PLEASE do read the posting guide
>and provide commented, minimal, self-contained, reproducible code.
Sent from my phone. Please excuse my brevity.
Remail@example.com mailing list -- To UNSUBSCRIBE and more, see
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.