|
![](/i/fill.gif) |
"clipka" <nomail@nomail> wrote:
> "Rahul" <nomail@nomail> wrote:
> > My errors seem pretty often too. Almost for every povray invocation.
>
> Well, those poor Xen victims talk about up to, like, 40 messages a second, so
> consider yourself lucky ;)
:) now if I were running a ray-tracing server-farm.....
--
Rahul
Post a reply to this message
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
Rahul nous illumina en ce 2009-01-30 14:52 -->
> "clipka" <nomail@nomail> wrote:
>> "Rahul" <nomail@nomail> wrote:
>
>> Do you happen to be running Xen?
>
> No. No Xen. Its a raw server. No virtualization at all.
>
>> I just did a quick google for "4gb seg fixup" and found zillions of entries, all
>> related to Xen as it seems -
>
> Ah! I guess I always searched for povray+"4gb seg fixup" and so never came
> across those entries. I'll see if I can somehow relate them to my problems.
>
> the quintessence of the articles being that the
>> severity of the messages probably ranges from cosmetic to a performance issue
>> (depending on how frequent they appear), that it affects various different
>> programs running under Xen, and that you need to replace a certain library with
>> a "Xen-friendly" version to get rid of this (details are mentioned in most all
>> the googled articles).
>
> My errors seem pretty often too. Almost for every povray invocation.
>
> --
> Rahul
>
>
Once per invocation is little. Once a minute or two is very little.
Once a second is moderate.
Several times a second is frequent.
--
Alain
-------------------------------------------------
You know you've been raytracing too long when you call in sick in order to render.
David Kraics
Post a reply to this message
|
![](/i/fill.gif) |