linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vadiraj <vadiraj.cs@gmail.com>
To: linux-c-programming <linux-c-programming@vger.kernel.org>
Subject: time system call expensive?
Date: Thu, 21 Jul 2011 10:11:14 +0530	[thread overview]
Message-ID: <CA+NBAy6499cgdzwGuPk6h+Y3D-DxEHP2HEKjtNAgis7K4RTKig@mail.gmail.com> (raw)

Hi All,

I'm evaluating time consumed by method. I'm using time(NULL) system
call to capture time before and after the call to the function.
Just wanted to know if this has a considerable performance hit? For
all I believe time syscall is quite optimized and should not really be
matter of concern.

Please let me know if someone have evaluated time(NULL) system over head..

Assuming the method I'm evaluating is a frequently called method.


Thanks in advance.

Regards,
Vadi

             reply	other threads:[~2011-07-21  4:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-21  4:41 Vadiraj [this message]
2011-07-21 11:20 ` time system call expensive? Michal Nazarewicz
2011-07-21 11:46   ` Akos Marton
2011-07-22  4:57     ` Vadiraj

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+NBAy6499cgdzwGuPk6h+Y3D-DxEHP2HEKjtNAgis7K4RTKig@mail.gmail.com \
    --to=vadiraj.cs@gmail.com \
    --cc=linux-c-programming@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).