Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6693247
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T05:57:38+00:00 2026-05-26T05:57:38+00:00

I think I must be misunderstanding something about R’s system.time() function. If I have

  • 0

I think I must be misunderstanding something about R’s system.time() function. If I have the following code in a test.r:

for(i in 1:10)
{
    print(system.time(testFunction()))
}

(where testFunction() is defined elsewhere, but contains some fairly computationally-intensive code), and run the code, but kill the job after the 1st loop, then receive the following output:

> source("test.r")
user  system elapsed
280.388   2.622 288.155
Timing stopped at: 210.891 0.367 211.637

why is the value for ‘Timing Stopped’ less than the elapsed time for the function?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T05:57:39+00:00Added an answer on May 26, 2026 at 5:57 am

    The timing restarts during the second loop, and since you killed it part way through, it will be less than what you timed for the full first loop.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Ok so I think I must be misunderstanding something about SQL queries. This is
I have the following code that shows either a bug or a misunderstanding on
I think I must be doing something wrong here because my code only sent
Why is 10000000000000.126.toString() 1000000000000.127 and 100000000000.126.toString() not? I think it must have something to
This must be a misunderstanding from my side, but I have the following: I
I'm trying to find a way to to do something that I think must
I think this must be simple but I can't get it right... I have
I think there must be something subtle going on here that I don't know
Some of the features I think it must include are: Print Entire Solution Ability
I am trying to do the following but I think I must be missing

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.