Artur,
        Thanks for the correction. I've certainly over look that there exist
a crossover point between the 2 ends. :-)

- Chien Yang
  Java 3D Team.

>Date: Fri, 05 Apr 2002 10:50:43 +0200
>From: Artur Biesiadowski <[EMAIL PROTECTED]>
>Subject: Re: [JAVA3D] A basic doubt
>To: [EMAIL PROTECTED]
>MIME-version: 1.0
>Content-transfer-encoding: 7bit
>X-Accept-Language: en-us, en
>Delivered-to: [EMAIL PROTECTED]
>User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.9)
Gecko/20020311
>
>Chien Yang wrote:
>> Raj,
>>         Let's do some math. A sphere geometry with resolution 15 division,
>> in Java 3D, will generate 480 vertices. Let's assume only coord. and normal
>> is needed, each sphere requires a minmum of 480 * 24 = 11520 bytes.
>> That is likely to be 4X the memory footprint of TransformGroup + Shape3D +
>> shared Geometry (~3600 bytes, calculated base on 50K spheres).
>
>I still think it is beneficial. With single sphere per geometry we have
>
>50k x 3600 + 1 x 11520
>180000k + 11520 ~= 180012k
>
>With for example 20 spheres per geometry/shape we have
>
>50k/20*3600 + 20x11520
>9000k + 440k = 9440k
>
> From 180MB -> 9MB. I think there is a benefit. Even for a larger
>geometries.
>
>
>Artur
>
>===========================================================================
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff JAVA3D-INTEREST".  For general help, send email to
>[EMAIL PROTECTED] and include in the body of the message "help".

===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST".  For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".

Reply via email to