floating point multiply == very very slow ?

by **Presto** » Oct 22, 2004 @ 4:07pm

If you're trying to do 630,000 operations per second, and getting 5-10fps, assume the worst case of 5fps and divide the number of operations by 6 to find a safe number of operations that should still get you 30fps... which is 105,000 operations maximum.

Divide 105,000 by 30fps and you should have a maximum of 3500 operations per frame. With 100 objects, that's 35 operations per object, per frame, rather than the 210 you're currently doing.

You definitely need a more simplistic approach.

-John

by **jaguard** » Oct 22, 2004 @ 4:35pm

by **warmi** » Oct 22, 2004 @ 4:39pm

by **jaguard** » Oct 22, 2004 @ 4:54pm

by **mlepage** » Oct 22, 2004 @ 5:13pm

by **jaguard** » Oct 23, 2004 @ 4:51pm

by hm » Oct 23, 2004 @ 6:51pm

by **fast_rx** » Oct 23, 2004 @ 9:17pm

Speaking of re-inventing a wheel...

Your atan function can be completely replaced by atan2(dx, dy)
(it does the quadrant stuff for you)

by **xPeterx** » Oct 24, 2004 @ 12:27pm

by **mm40** » Oct 29, 2004 @ 2:28pm

by **jaguard** » Oct 30, 2004 @ 12:23am

floating point multiply == very very slow ?

Re: floating point multiply == very very slow ?

Sort

Forum Description

Moderators:

Forum permissions