Re: [Bigdata-developers] Java 7?

[Bryan T. <br...@sy...>]

Another big advantage of Java 7 is that the G1 garbage collector finally
appears to work.  This means that you can start to use larger heaps.  I
have not yet felt out the rough spots here, but that is an exciting
development.
Bryan

On 8/28/13 4:45 PM, "Peter Ansell" <ans...@gm...> wrote:

>It would only be an issue in the case you say. From a users point of view
>not much changes, comparatively, which is the main reason for not doing
>it from my impressions.
>
>It will be nice to see the performance boosts from the new methods.
>
>--
>Peter
>
>On 29/08/2013, at 6:34 AM, Jeremy J Carroll <jj...@sy...> wrote:
>
>> presumably it isn't an issue for us if the sesame code remains java 6
>>compatible?
>> A minor detail is that we may mistakenly suggest non-compatible bug
>>fixes to themŠ
>> 
>> Jeremy J Carroll
>> Principal Architect
>> Syapse, Inc.
>> 
>> 
>> 
>> On Aug 28, 2013, at 1:31 PM, Bryan Thompson <br...@sy...> wrote:
>> 
>>> Thing thing which is forcing this issue is work that we are doing on
>>>graph
>>> mining on RDF graphs.  Threading is a big issue there.  Access to AIO,
>>> parallelized sorts, and fork/join pools could really help out as well.
>>> This would in turn be a good opportunity to move the platform to take
>>> advantage of those features in the QueryEngine.  As originally
>>>designed,
>>> we need to use unbounded thread pools because all IOs can block.  A
>>> fork/join pattern might produce significant performance gains.  This is
>>> easier to test in the context of the RDF graph mining since that code
>>>is
>>> new, but I think that this would apply to query as well.
>>> 
>>> Thanks,
>>> Bryan
>>> 
>>> On 8/28/13 4:27 PM, "Peter Ansell" <ans...@gm...> wrote:
>>> 
>>>> 
>>>> On 29/08/2013, at 5:03 AM, Bryan Thompson <br...@sy...> wrote:
>>>> 
>>>>> Any thoughts on switching to Java 7 as a requirement?  So far we have
>>>>> maintained Java 6 compatibility.  However, there are new threading
>>>>> patterns in Java 7 that could be very useful.  There is also the
>>>>> asynchronous file IO support.  Java 7 had some very bad initial
>>>>> releases, but seems to be Ok now and Oracle has sunset Java 6.
>>>>> 
>>>>> Thanks,
>>>>> Bryan
>>>> 
>>>> The Sesame API and core is indefinitely going to stay at Java6
>>>> compatibility from what I can tell. My Java7 patches to add support
>>>>for
>>>> autocloseable were vetoed by the main companies backing the other
>>>> developers as not worthwhile. That, and native support for BCP47 were
>>>>the
>>>> main drivers for updating the API in my view. The threading and file
>>>>io
>>>> changes don't directly impact the core enough to convince them of it
>>>>as
>>>> far as I can tell.
>>>> 
>>>> Peter
>>> 
>>> 
>>> 
>>>------------------------------------------------------------------------
>>>------
>>> Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
>>> Discover the easy way to master current and previous Microsoft
>>>technologies
>>> and advance your career. Get an incredible 1,500+ hours of step-by-step
>>> tutorial videos with LearnDevNow. Subscribe today and save!
>>> 
>>>http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clk
>>>trk
>>> _______________________________________________
>>> Bigdata-developers mailing list
>>> Big...@li...
>>> https://lists.sourceforge.net/lists/listinfo/bigdata-developers
>>