public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Pamulapati, Indrasena (CTS)" <pindrase@chn.cognizant.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Performance comparision
Date: Tue, 06 Feb 2001 08:22:00 -0000	[thread overview]
Message-ID: <8F1D166D08ACD41196EE00B0D020944BA9A843@CTSINENTSXUB> (raw)

Hi,

I am the same guy who asked about the problem of having a very high tick
rate for addressing very small time units.
I now perfectly understand the futility of increasing the tick rate to very
high value and have decided to use external timers to address small time
frames.

But just for comparision, I ported my application to VRTXsa a different
RTOS. And I used the same high tick rate ( about 10000 ticks per second) and
the application was running fine. I was able to acheive the bit rate of
about 20Mbps that I was suppose to acheive. But in eCos with such high tick
value I was able to acheive only 4Mbps.

In reply to my previous mail I understood that if we use a very high tick
value a lot of processor resources will be spent on processing the tick only
and my application will suffer. But why am i not facing the same problem in
VRTXsa?

Is it a limitation of eCos?

Thankyou,

indrasena
 

This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information.
If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. 
Any unauthorised review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly 
prohibited and may be unlawful.

		Visit us at http://www.cognizant.com

             reply	other threads:[~2001-02-06  8:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-06  8:22 Pamulapati, Indrasena (CTS) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-06  5:50 Pamulapati, Indrasena (CTS)
2001-02-06  6:55 ` Jonathan Larmour

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=8F1D166D08ACD41196EE00B0D020944BA9A843@CTSINENTSXUB \
    --to=pindrase@chn.cognizant.com \
    --cc=ecos-discuss@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).