Posted by
Michael Bien on
Jan 25, 2011; 6:15pm
URL: https://forum.jogamp.org/method-not-implemented-gluScaleImage-tp2304656p2332650.html
On 01/25/2011 05:16 PM, Sven Gothel [via jogamp] wrote:
>
> On Tuesday, January 25, 2011 17:04:47 Wade Walker [via jogamp] wrote:
>> Submitted this fix and a unit test at
>>
https://github.com/sgothel/jogl/pull/20.
>>
>> Julien, I totally agree that allocating one big direct buffer and slicing it
>> would be faster. However, since we're trying to fix bugs to finalize the
>> JOGL 2 release, I don't want to change any more code than the absolute
>> minimum right now. We can submit an enhancement later if users say they
>> could benefit from improved speed here
>>
> There would be another tool useful in this regard,
> nio lazy buffers (nlb).
> nlb would
> - instantiate NIO lazy when needed
> - use common nio mem pool
prob with pools: multithreading, fragmentation (esp both in combination)
-> makes it very hard to do it "right"
but... yes we have to go this path earlier or later. Maybe even decide
case-to case instead of a generic pooling api how we want to solve that.
E.g as already mentioned in jocl i have different kind of static
allocated / lazy allocated memory. For instance threadlocal for per
thread command queues and lazy + synchronized for not performance
critical code (e.g cachable hw information queries).
... continuing with my boring exam preparations.. :(
-michael