Jim,
There are finally only few growable arrays (edges, curves, rowAARLE) and
now I have a working Pisces code (J2DBench pass OK) that performs better
than current (2x - 3x faster on dasher or big shapes) using only few
megabytes (Xmx32m) ...
Moreover, these arrays could be created once per
Andrea,
thanks for these estimates / stats.
I think such use case could benefit a lot from my patch (low memory
footprint) but thread-safe cached / reused arrays/ LineIteratorData /
StrokerData / DasherData.
As I said to Jim, there are two sort of problems:
- memory handling (growable arrays)
On 26/03/2013 19:29, Dan Xu wrote:
Hi All,
In the old JVM function, os::available, it could return negative
values because lseek() allows the file offset to be set beyond the end
of a file. In the previous change of removing jvm functions, I wasn't
aware of that and regardnegative values as
I see. So we will need clarify the spec and make corresponding changes.
I think as long as we don't trigger exceptions and just return 0 will be
backward-compatible, right?
-Dan
On 03/30/2013 10:23 AM, Alan Bateman wrote:
On 26/03/2013 19:29, Dan Xu wrote:
Hi All,
In the old JVM function,
