linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Klaas van Gend <klaas.van.gend@mvista.com>
Cc: jordan <triplesquarednine@gmail.com>, Raz <raziebe@gmail.com>,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: preempt rt in commercial use
Date: Wed, 15 Sep 2010 07:03:17 -0700	[thread overview]
Message-ID: <4C90D225.1080902@us.ibm.com> (raw)
In-Reply-To: <201009151059.23039.klaas.van.gend@mvista.com>

Klaas van Gend wrote:
> On Wednesday 15 September 2010 05:38:49 jordan wrote:
>> Which leads me to my last example. Most people are aware that since
>> about 1999-2000, Linux has dominated the movie industry. Beginning
>> with Titanic and even today with say, Avatar.
>>
>> I would be willing to bet, that all of those wonderful rendering farms
>> and production suites, are
>> in fact using rt-linux.
> 
> 
> Please put a lot of money on that bet, because I'd like to win it :-)
> 
> Why would those rendering farms use rt-linux?
> 
> Rendering is not done in real-time - far from it actually. It can take minutes 
> of the entire farm to render a single frame. So rendering is nothing but CPU-
> intensive (calculating how all those lightbeams are reflected by each surface) 
> - and everything I/O bound is about throughput: writing the rendered pixels to 
> disk and getting more surfaces from disk.
> 
> There are no deadlines for rendering, there are no penalties if a frame is 
> late by seconds - if the farm cannot complete its job overnight, they'll add 
> more CPU power.

While all of the above is true, I'll add that it's worth testing
RT because certain applications which have lock-step operations,
can be very negatively impacted in throughput by severe lack of
determinism.  If all of a set of operations need to complete before
they can do the next set of operations, and one of the threads takes
very long, the others all idle as a result. If this happens frequently,
you're better off trying to cap max latencies.

So RT actually provides improved *throughput* as well, despite the
increased overhead.

I don't know if these rendering type applications necessarily
fall into that bucket, but I would at least take a look.


thanks,
Nivedita



  parent reply	other threads:[~2010-09-15 14:04 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-14  8:10 preempt rt in commercial use Raz
2010-09-14  9:04 ` Rolando Martins
2010-09-14  9:10   ` Raz
2010-09-14  9:20     ` Rolando Martins
2010-09-14  9:17 ` Nikita V. Youshchenko
2010-09-14  9:24   ` Raz
2010-09-14  9:44     ` Robert Schwebel
2010-09-14 12:16       ` Armin Steinhoff
2010-09-14 13:04         ` Daniel James
2010-09-14 13:08         ` Pradyumna Sampath
2010-09-14 22:11           ` Nivedita Singhvi
2010-09-14 13:09         ` Klaas van Gend
2010-09-14 13:17         ` David Kastrup
2010-09-14 13:37           ` Darcy Watkins
2010-09-14 13:58         ` Patrice Kadionik
2010-09-14 14:21       ` Jeff Angielski
2010-09-14 14:30         ` Nikita V. Youshchenko
2010-09-14 14:49           ` Jeff Angielski
2010-09-14 22:20             ` Nivedita Singhvi
2010-09-15  7:48               ` Armin Steinhoff
2010-09-15 14:09                 ` Nivedita Singhvi
2010-09-15 14:45                   ` Pradyumna Sampath
2010-09-16 10:17                     ` Daniel James
2010-09-16 10:35                       ` Pradyumna Sampath
2010-09-16 15:19                       ` Raz
2010-09-15 15:38                   ` David Kastrup
2010-09-15 16:02                     ` Nivedita Singhvi
2010-09-15 16:20                       ` David Kastrup
2010-09-16  0:44                         ` Steven Rostedt
2010-09-16 15:27                           ` Nivedita Singhvi
2010-09-16 17:30                             ` Steven Rostedt
2010-09-16 19:27                               ` Armin Steinhoff
2010-09-16 19:38                                 ` Steven Rostedt
2010-09-15 13:33             ` Thomas Gleixner
2010-09-14 14:44         ` Pradyumna Sampath
2010-09-15 12:48           ` Sergio Ruocco
2010-09-15 12:53             ` Pradyumna Sampath
2010-09-15 14:58             ` Paul E. McKenney
2010-09-15 16:27             ` Sven-Thorsten Dietrich
2010-09-16  0:49               ` Steven Rostedt
2010-09-16  5:06                 ` David Kastrup
2010-09-14 14:56         ` Armin Steinhoff
2010-09-14 15:42         ` Patrice Kadionik
2010-09-14 17:38         ` Gregory Haskins
2010-09-14 22:09           ` Nivedita Singhvi
2010-09-15  6:22             ` Patrice Kadionik
     [not found]               ` <4C90CF71.2050205@us.ibm.com>
2010-09-15 13:56                 ` Patrice Kadionik
2010-09-15 14:08               ` Steven Rostedt
2010-09-14 10:06   ` Klaas van Gend
2010-09-14 11:00     ` David Kastrup
2010-09-14  9:28 ` Pradyumna Sampath
2010-09-14 14:13 ` Reagan Thomas
2010-09-15  7:09   ` AW: " Lukas Redlinger
2010-09-15  3:38 ` jordan
2010-09-15  8:59   ` Klaas van Gend
2010-09-15 11:03     ` TinxCore and PREEMPT_RT Armin Steinhoff
2010-09-16  9:38       ` Armin Steinhoff
2010-09-16 10:18         ` David Kastrup
2010-09-16 11:25           ` Mike Galbraith
2010-09-16 11:51           ` Armin Steinhoff
2010-09-15 14:03     ` Nivedita Singhvi [this message]
2010-09-15 17:29       ` preempt rt in commercial use Reagan Thomas
2010-09-16 10:39         ` Daniel James
2010-09-16 20:47           ` jordan
2010-09-16 10:07   ` Daniel James
2010-09-16 20:37     ` jordan

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=4C90D225.1080902@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=klaas.van.gend@mvista.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=raziebe@gmail.com \
    --cc=triplesquarednine@gmail.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 NNTP newsgroup(s).