javax GC API

[Suminda Dharmasena]

Hi,

Proper escape analysis can eliminate the need of GC. I
cannot understand why Oracle (Sun before oracle) choose to carry the burden
of the GC. This creates:

   - Memory footprint
   - Processing footprint
   - GC pause

With proper escape analysis and allocating in the stack GC can
be eliminated in most cases. Also finalising can be eliminated.

Annotations can be used what point exactly the resource is released. This
will take only fraction of nanoseconds but this also will be known.

Also collection can happen in a deferred mode as this is what needs to be
GCed. Ideally this should be reserved for IO pause applications which can
run the GC thread on pause.

Suminda
--
Suminda Sirinath Salpitikorala Dharmasena, B.Sc. Comp. & I.S. (Hon.) Lond.,
P.G.Dip. Ind. Maths. J'Pura, MIEEE, MACM, CEO Sakrīō! ▣ *Address*: 6G • 1st
Lane • Pagoda Road • Nugegoda 10250 • Sri Lanka. ▣ *Tele*: +94-(0)11-5
864614 / 5 875614 / 2 825908 ▣ *Web*: http://www.sakrio.com ▣

This email is subjected to the email Terms of Use and Disclaimer:
http://www.sakrio.com/email-legal. Please read this first.
--


On 22 April 2013 19:45, Ryan Gardner <ryebrye at gmail.com> wrote:

> On Fri, Apr 19, 2013 at 6:04 AM, Suminda Dharmasena <sirinath at sakrio.com>wrote:
>
>> Also if the programmer fails to wisely GC using API / Annotations then
>> the fallback is the default GC mechanism. This way there will be no memory
>> leaks. Also objects which are GCed will be objects that can be GCed. Live /
>> referenced objects which escape the explicit GC context will not be GCed.
>>
>> The objective is that:
>>
>>    - The GC check happens at define points in code
>>    - GC happens at define points if possible, else fall back to the
>>    system GC mechanism
>>
>> How will this work with multithreaded environments like a web server?
>
> The stop-the-world phases of GC by definition stop more than just one
> thread?
>
> Also this seems very JVM vendor specific - I can't imagine the Azul guys
> (who market their JVM as if GC pauses don't exist at all on their VM) would
> care about this, nor would the IBM guys likely care.
>
> The specific annotations proposed also do not follow the best practice for
> naming annotations - they explicitly define a specific behavior to take as
> a result of the annotation being applied.
>
> I'm just a community member, and not a hotspot engineer or contributor -
> but I can wholeheartedly say that I would never use these annotations and I
> would never use code from any open source project that littered their
> project with these annotations.
>
>
>
>>
>> _______________________________________________
>> hotspot-gc-use mailing list
>> hotspot-gc-use at openjdk.java.net
>> http://mail.openjdk.java.net/mailman/listinfo/hotspot-gc-use
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/hotspot-gc-use/attachments/20130422/efc5812f/attachment.html