[Imstk-developers] Mesh load factor

[Sreekanth Arikatla]

sounds good. Can we call it 'resizing factor' then?

On Fri, Sep 29, 2017 at 3:54 PM, Milef, Nicholas Boris <milefn at rpi.edu>
wrote:

> Well, I was thinking of just having a limit. So if you load a mesh that's
> 10k vertices, and it's load factor is 2x, then you can't add more than 20k
> vertices.
> ------------------------------
> *From:* Sreekanth Arikatla [sreekanth.arikatla at kitware.com]
> *Sent:* Friday, September 29, 2017 3:50 PM
> *To:* Milef, Nicholas Boris
> *Cc:* imstk-developers at imstk.org
> *Subject:* Re: [Imstk-developers] Mesh load factor
>
> Can you explain a bit more? Do you plan to do a fresh allocation when
> resizing mesh beyond a certain size to prevent fragmentation?
>
> On Fri, Sep 29, 2017 at 1:56 PM, Milef, Nicholas Boris <milefn at rpi.edu>
> wrote:
>
>> What do you all think about a mesh load factor? I would like to add one
>> to prevent a range of allocations issues (fragmentation, invalid
>> allocations, etc.) when resizing a mesh. This would be able to be
>> customized by the user of course.
>>
>> _______________________________________________
>> Imstk-developers mailing list
>> Imstk-developers at imstk.org
>> http://public.kitware.com/mailman/listinfo/imstk-developers
>>
>>
>
>
> --
> Sreekanth Arikatla, Ph.D.,
> Senior R&D Engineer,
> Kitware, Inc. <http://www.kitware.com>, Carrboro, NC.
>
>


-- 
Sreekanth Arikatla, Ph.D.,
Senior R&D Engineer,
Kitware, Inc. <http://www.kitware.com>, Carrboro, NC.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/imstk-developers/attachments/20170929/55bbed66/attachment.html>