visualpython-users

[Visualpython-users] nested frames, cpu times

[Kuzminski, S. R <SKu...@fa...>]

My vpython app takes up 50% or so of the cpu just sitting there ( on a
windows box ).  I put a sleep in my top level loop, but it didn't seem
to help, maybe there is a thread eating up lots of cpu within vpython?

=20

also,

=20

Can I nest frames within frames?

=20

thanks,

S

Re: [Visualpython-users] nested frames, cpu times

[Bruce S. <Bru...@nc...>]

That's odd. I ran lathe.py from the VPython demo suite and observed CPU=20
usage, which was less than 1% on a 2.6 GHz Windows XP machine. Note that=20
lathe.py makes a display and then ends. Even running stonehenge.py,=20
which has a continuous animation and looks for user mouse inputs, runs=20
at less that 1%. There is a rendering thread which many times per second=20
renders the scene, and it isn't "smart" -- it doesn't do any=20
optimization but every time clears some memory to black and repaints the=20
whole scene. But this is a fast process.

Yes, you can nest frames within frames.

Bruce Sherwood

Kuzminski, Stefan R wrote:

> My vpython app takes up 50% or so of the cpu just sitting there ( on a=20
> windows box ).  I put a sleep in my top level loop, but it didn=92t see=
m=20
> to help, maybe there is a thread eating up lots of cpu within vpython?
>=20
> also,
>=20
> Can I nest frames within frames?
>=20
> thanks,
>=20
> S

Re: [Visualpython-users] nested frames, cpu times

[Jonathan B. <jbr...@ea...>]

On Wed, 2004-05-12 at 15:55, Kuzminski, Stefan R wrote:
> My vpython app takes up 50% or so of the cpu just sitting there ( on a
> windows box ).  I put a sleep in my top level loop, but it didn=FFt seem
> to help, maybe there is a thread eating up lots of cpu within vpython?

Yes.  Your changes are updated to the screen immediately because the
entire scene is being rendered repeatedly at not more than 30 fps in a
background thread, thus giving the appearance of being updated
instantly.  If the scene is particularly complex, it will eat up a lot
more CPU time.  Convex objects, curves with non-zero thickness, and
faces objects are the worst performers right now.

> Can I nest frames within frames?

Yes.  You cannot have a cycle of frames, such as a frame within itself,
even indirectly.  VPython will catch this kind of error and raise an
exception.

HTH,
Jonathan Brandmeyer