You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by asookazian2 <as...@gmail.com> on 2014/03/03 22:55:59 UTC
performance metrics blueprint vs. declarative services in karaf
3.0.x
Any info on perf metrics on DS vs. BP? thx.
--
View this message in context: http://karaf.922171.n3.nabble.com/performance-metrics-blueprint-vs-declarative-services-in-karaf-3-0-x-tp4032028.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: performance metrics blueprint vs. declarative services in karaf 3.0.x
Posted by Ryan Moquin <fr...@gmail.com>.
Gotcha.. that would make a lot of sense.
On Mar 4, 2014 12:31 PM, "Achim Nierbeck" <bc...@googlemail.com> wrote:
> I second you on most of this,
> my personal view on this topic, the only advantage is the possibility to
> change the blueprint implementation by the user, because Karaf itself
> doesn't depend on it anymore.
> But that is basically it.
>
> regards, Achim
>
>
> 2014-03-04 17:24 GMT+01:00 Ryan Moquin <fr...@gmail.com>:
>
>> That's right, you mentioned size before. My bad, thanks! I personally
>> think DS is more confusing, but to each his own.
>>
>> Ryan
>> On Mar 4, 2014 11:20 AM, "Jamie G." <ja...@gmail.com> wrote:
>>
>>> Largest advantage is allowing for an even smaller minimal Karaf
>>> distribution to be made - the full distribution would include the BP
>>> feature by default.
>>>
>>> Other than that there are various discussions abound on DS vs BP. Each
>>> have their strengths and weaknesses, and developer tastes.
>>>
>>> --Jamie
>>>
>>> On Tue, Mar 4, 2014 at 12:20 PM, Ryan Moquin <fr...@gmail.com>
>>> wrote:
>>> > What's the advantage in switching to DS in Karaf 4.x then?
>>> >
>>> > On Mar 4, 2014 2:37 AM, "Achim Nierbeck" <bc...@googlemail.com>
>>> wrote:
>>> >>
>>> >> I don't think there are any awailable yet,
>>> >> and actually I don't expect there to be much of a difference.
>>> >> Both are basically doing the same thing.
>>> >> Blueprint does have an extender that will do the wiring for you,
>>> >> so there might be a "overhead" on the start of the bundle ...
>>> >> but I don't expect there to be an overhead later on, or at least not
>>> >> significant.
>>> >> DS is just a "convenience-wrapper" for standard OSGi technology.
>>> >> During build-time the BND or what ever will transform the annotations
>>> to
>>> >> Service-Trackers and Service Registrations.
>>> >>
>>> >> At the end it boils down to services and service-trackers that are
>>> >> "hidden" for the user, either by a xml syntax and an extender, or an
>>> >> annotation and a build time enhancement.
>>> >>
>>> >> regards, Achim
>>> >>
>>> >>
>>> >>
>>> >> 2014-03-03 22:55 GMT+01:00 asookazian2 <as...@gmail.com>:
>>> >>>
>>> >>> Any info on perf metrics on DS vs. BP? thx.
>>> >>>
>>> >>>
>>> >>>
>>> >>> --
>>> >>> View this message in context:
>>> >>>
>>> http://karaf.922171.n3.nabble.com/performance-metrics-blueprint-vs-declarative-services-in-karaf-3-0-x-tp4032028.html
>>> >>> Sent from the Karaf - User mailing list archive at Nabble.com.
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >>
>>> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>>> >> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>>> Committer &
>>> >> Project Lead
>>> >> blog <http://notizblog.nierbeck.de/>
>>> >>
>>> >> Software Architect / Project Manager / Scrum Master
>>> >>
>>> >
>>>
>>
>
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> blog <http://notizblog.nierbeck.de/>
>
> Software Architect / Project Manager / Scrum Master
>
>
Re: performance metrics blueprint vs. declarative services in karaf 3.0.x
Posted by Achim Nierbeck <bc...@googlemail.com>.
I second you on most of this,
my personal view on this topic, the only advantage is the possibility to
change the blueprint implementation by the user, because Karaf itself
doesn't depend on it anymore.
But that is basically it.
regards, Achim
2014-03-04 17:24 GMT+01:00 Ryan Moquin <fr...@gmail.com>:
> That's right, you mentioned size before. My bad, thanks! I personally
> think DS is more confusing, but to each his own.
>
> Ryan
> On Mar 4, 2014 11:20 AM, "Jamie G." <ja...@gmail.com> wrote:
>
>> Largest advantage is allowing for an even smaller minimal Karaf
>> distribution to be made - the full distribution would include the BP
>> feature by default.
>>
>> Other than that there are various discussions abound on DS vs BP. Each
>> have their strengths and weaknesses, and developer tastes.
>>
>> --Jamie
>>
>> On Tue, Mar 4, 2014 at 12:20 PM, Ryan Moquin <fr...@gmail.com>
>> wrote:
>> > What's the advantage in switching to DS in Karaf 4.x then?
>> >
>> > On Mar 4, 2014 2:37 AM, "Achim Nierbeck" <bc...@googlemail.com>
>> wrote:
>> >>
>> >> I don't think there are any awailable yet,
>> >> and actually I don't expect there to be much of a difference.
>> >> Both are basically doing the same thing.
>> >> Blueprint does have an extender that will do the wiring for you,
>> >> so there might be a "overhead" on the start of the bundle ...
>> >> but I don't expect there to be an overhead later on, or at least not
>> >> significant.
>> >> DS is just a "convenience-wrapper" for standard OSGi technology.
>> >> During build-time the BND or what ever will transform the annotations
>> to
>> >> Service-Trackers and Service Registrations.
>> >>
>> >> At the end it boils down to services and service-trackers that are
>> >> "hidden" for the user, either by a xml syntax and an extender, or an
>> >> annotation and a build time enhancement.
>> >>
>> >> regards, Achim
>> >>
>> >>
>> >>
>> >> 2014-03-03 22:55 GMT+01:00 asookazian2 <as...@gmail.com>:
>> >>>
>> >>> Any info on perf metrics on DS vs. BP? thx.
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> View this message in context:
>> >>>
>> http://karaf.922171.n3.nabble.com/performance-metrics-blueprint-vs-declarative-services-in-karaf-3-0-x-tp4032028.html
>> >>> Sent from the Karaf - User mailing list archive at Nabble.com.
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >>
>> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> >> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>> Committer &
>> >> Project Lead
>> >> blog <http://notizblog.nierbeck.de/>
>> >>
>> >> Software Architect / Project Manager / Scrum Master
>> >>
>> >
>>
>
--
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Software Architect / Project Manager / Scrum Master
Re: performance metrics blueprint vs. declarative services in karaf 3.0.x
Posted by Ryan Moquin <fr...@gmail.com>.
That's right, you mentioned size before. My bad, thanks! I personally
think DS is more confusing, but to each his own.
Ryan
On Mar 4, 2014 11:20 AM, "Jamie G." <ja...@gmail.com> wrote:
> Largest advantage is allowing for an even smaller minimal Karaf
> distribution to be made - the full distribution would include the BP
> feature by default.
>
> Other than that there are various discussions abound on DS vs BP. Each
> have their strengths and weaknesses, and developer tastes.
>
> --Jamie
>
> On Tue, Mar 4, 2014 at 12:20 PM, Ryan Moquin <fr...@gmail.com>
> wrote:
> > What's the advantage in switching to DS in Karaf 4.x then?
> >
> > On Mar 4, 2014 2:37 AM, "Achim Nierbeck" <bc...@googlemail.com>
> wrote:
> >>
> >> I don't think there are any awailable yet,
> >> and actually I don't expect there to be much of a difference.
> >> Both are basically doing the same thing.
> >> Blueprint does have an extender that will do the wiring for you,
> >> so there might be a "overhead" on the start of the bundle ...
> >> but I don't expect there to be an overhead later on, or at least not
> >> significant.
> >> DS is just a "convenience-wrapper" for standard OSGi technology.
> >> During build-time the BND or what ever will transform the annotations to
> >> Service-Trackers and Service Registrations.
> >>
> >> At the end it boils down to services and service-trackers that are
> >> "hidden" for the user, either by a xml syntax and an extender, or an
> >> annotation and a build time enhancement.
> >>
> >> regards, Achim
> >>
> >>
> >>
> >> 2014-03-03 22:55 GMT+01:00 asookazian2 <as...@gmail.com>:
> >>>
> >>> Any info on perf metrics on DS vs. BP? thx.
> >>>
> >>>
> >>>
> >>> --
> >>> View this message in context:
> >>>
> http://karaf.922171.n3.nabble.com/performance-metrics-blueprint-vs-declarative-services-in-karaf-3-0-x-tp4032028.html
> >>> Sent from the Karaf - User mailing list archive at Nabble.com.
> >>
> >>
> >>
> >>
> >> --
> >>
> >> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> >> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/>
> Committer &
> >> Project Lead
> >> blog <http://notizblog.nierbeck.de/>
> >>
> >> Software Architect / Project Manager / Scrum Master
> >>
> >
>
Re: performance metrics blueprint vs. declarative services in karaf 3.0.x
Posted by "Jamie G." <ja...@gmail.com>.
Largest advantage is allowing for an even smaller minimal Karaf
distribution to be made - the full distribution would include the BP
feature by default.
Other than that there are various discussions abound on DS vs BP. Each
have their strengths and weaknesses, and developer tastes.
--Jamie
On Tue, Mar 4, 2014 at 12:20 PM, Ryan Moquin <fr...@gmail.com> wrote:
> What's the advantage in switching to DS in Karaf 4.x then?
>
> On Mar 4, 2014 2:37 AM, "Achim Nierbeck" <bc...@googlemail.com> wrote:
>>
>> I don't think there are any awailable yet,
>> and actually I don't expect there to be much of a difference.
>> Both are basically doing the same thing.
>> Blueprint does have an extender that will do the wiring for you,
>> so there might be a "overhead" on the start of the bundle ...
>> but I don't expect there to be an overhead later on, or at least not
>> significant.
>> DS is just a "convenience-wrapper" for standard OSGi technology.
>> During build-time the BND or what ever will transform the annotations to
>> Service-Trackers and Service Registrations.
>>
>> At the end it boils down to services and service-trackers that are
>> "hidden" for the user, either by a xml syntax and an extender, or an
>> annotation and a build time enhancement.
>>
>> regards, Achim
>>
>>
>>
>> 2014-03-03 22:55 GMT+01:00 asookazian2 <as...@gmail.com>:
>>>
>>> Any info on perf metrics on DS vs. BP? thx.
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://karaf.922171.n3.nabble.com/performance-metrics-blueprint-vs-declarative-services-in-karaf-3-0-x-tp4032028.html
>>> Sent from the Karaf - User mailing list archive at Nabble.com.
>>
>>
>>
>>
>> --
>>
>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
>> Project Lead
>> blog <http://notizblog.nierbeck.de/>
>>
>> Software Architect / Project Manager / Scrum Master
>>
>
Re: performance metrics blueprint vs. declarative services in karaf 3.0.x
Posted by Ryan Moquin <fr...@gmail.com>.
What's the advantage in switching to DS in Karaf 4.x then?
On Mar 4, 2014 2:37 AM, "Achim Nierbeck" <bc...@googlemail.com> wrote:
> I don't think there are any awailable yet,
> and actually I don't expect there to be much of a difference.
> Both are basically doing the same thing.
> Blueprint does have an extender that will do the wiring for you,
> so there might be a "overhead" on the start of the bundle ...
> but I don't expect there to be an overhead later on, or at least not
> significant.
> DS is just a "convenience-wrapper" for standard OSGi technology.
> During build-time the BND or what ever will transform the annotations to
> Service-Trackers and Service Registrations.
>
> At the end it boils down to services and service-trackers that are
> "hidden" for the user, either by a xml syntax and an extender, or an
> annotation and a build time enhancement.
>
> regards, Achim
>
>
>
> 2014-03-03 22:55 GMT+01:00 asookazian2 <as...@gmail.com>:
>
>> Any info on perf metrics on DS vs. BP? thx.
>>
>>
>>
>> --
>> View this message in context:
>> http://karaf.922171.n3.nabble.com/performance-metrics-blueprint-vs-declarative-services-in-karaf-3-0-x-tp4032028.html
>> Sent from the Karaf - User mailing list archive at Nabble.com.
>>
>
>
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> blog <http://notizblog.nierbeck.de/>
>
> Software Architect / Project Manager / Scrum Master
>
>
Re: performance metrics blueprint vs. declarative services in karaf 3.0.x
Posted by Ryan Moquin <fr...@gmail.com>.
Right, that wasn't my concern in regards to reasons for switching.. I just
want to make sure there isn't some big difference in general that might
sway me away from Blueprint. I just see it as the less Karaf has to
include by default just to run, the better.
Ryan
On Mar 4, 2014 3:59 PM, "Achim Nierbeck" <bc...@googlemail.com> wrote:
> Hi David,
>
> yep you're absolutely right, I've been on the wrong track somehow ...
> So yes, one shouldn't take my statement literally.
>
> At the end we agree on, that it doesn't make a difference for the user of
> Karaf if the
> wiring of Karaf Services is done this way or that way ;)
>
> regards, Achim
>
>
>
>
> 2014-03-04 21:09 GMT+01:00 David Jencks <da...@yahoo.com>:
>
>> Your view of DS does not match reality, unless perhaps you are being
>> entirely metaphorical in your description of how DS works. Taken
>> literally, each of your statements about DS is wrong.
>>
>> However, I agree with what I think is your conclusion that in all
>> plausible scenarios there's going to be no measurable performance
>> difference between blueprint and DS.
>>
>> thanks
>> david jencks
>>
>> On Mar 3, 2014, at 11:36 PM, Achim Nierbeck <bc...@googlemail.com>
>> wrote:
>>
>> I don't think there are any awailable yet,
>> and actually I don't expect there to be much of a difference.
>> Both are basically doing the same thing.
>> Blueprint does have an extender that will do the wiring for you,
>> so there might be a "overhead" on the start of the bundle ...
>> but I don't expect there to be an overhead later on, or at least not
>> significant.
>> DS is just a "convenience-wrapper" for standard OSGi technology.
>> During build-time the BND or what ever will transform the annotations to
>> Service-Trackers and Service Registrations.
>>
>> At the end it boils down to services and service-trackers that are
>> "hidden" for the user, either by a xml syntax and an extender, or an
>> annotation and a build time enhancement.
>>
>> regards, Achim
>>
>>
>>
>> 2014-03-03 22:55 GMT+01:00 asookazian2 <as...@gmail.com>:
>>
>>> Any info on perf metrics on DS vs. BP? thx.
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://karaf.922171.n3.nabble.com/performance-metrics-blueprint-vs-declarative-services-in-karaf-3-0-x-tp4032028.html
>>> Sent from the Karaf - User mailing list archive at Nabble.com.
>>>
>>
>>
>>
>> --
>>
>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer
>> & Project Lead
>> blog <http://notizblog.nierbeck.de/>
>>
>> Software Architect / Project Manager / Scrum Master
>>
>>
>>
>
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> blog <http://notizblog.nierbeck.de/>
>
> Software Architect / Project Manager / Scrum Master
>
>
Re: performance metrics blueprint vs. declarative services in karaf 3.0.x
Posted by Achim Nierbeck <bc...@googlemail.com>.
Hi David,
yep you're absolutely right, I've been on the wrong track somehow ...
So yes, one shouldn't take my statement literally.
At the end we agree on, that it doesn't make a difference for the user of
Karaf if the
wiring of Karaf Services is done this way or that way ;)
regards, Achim
2014-03-04 21:09 GMT+01:00 David Jencks <da...@yahoo.com>:
> Your view of DS does not match reality, unless perhaps you are being
> entirely metaphorical in your description of how DS works. Taken
> literally, each of your statements about DS is wrong.
>
> However, I agree with what I think is your conclusion that in all
> plausible scenarios there's going to be no measurable performance
> difference between blueprint and DS.
>
> thanks
> david jencks
>
> On Mar 3, 2014, at 11:36 PM, Achim Nierbeck <bc...@googlemail.com>
> wrote:
>
> I don't think there are any awailable yet,
> and actually I don't expect there to be much of a difference.
> Both are basically doing the same thing.
> Blueprint does have an extender that will do the wiring for you,
> so there might be a "overhead" on the start of the bundle ...
> but I don't expect there to be an overhead later on, or at least not
> significant.
> DS is just a "convenience-wrapper" for standard OSGi technology.
> During build-time the BND or what ever will transform the annotations to
> Service-Trackers and Service Registrations.
>
> At the end it boils down to services and service-trackers that are
> "hidden" for the user, either by a xml syntax and an extender, or an
> annotation and a build time enhancement.
>
> regards, Achim
>
>
>
> 2014-03-03 22:55 GMT+01:00 asookazian2 <as...@gmail.com>:
>
>> Any info on perf metrics on DS vs. BP? thx.
>>
>>
>>
>> --
>> View this message in context:
>> http://karaf.922171.n3.nabble.com/performance-metrics-blueprint-vs-declarative-services-in-karaf-3-0-x-tp4032028.html
>> Sent from the Karaf - User mailing list archive at Nabble.com.
>>
>
>
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
> Project Lead
> blog <http://notizblog.nierbeck.de/>
>
> Software Architect / Project Manager / Scrum Master
>
>
>
--
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Software Architect / Project Manager / Scrum Master
Re: performance metrics blueprint vs. declarative services in karaf 3.0.x
Posted by David Jencks <da...@yahoo.com>.
Your view of DS does not match reality, unless perhaps you are being entirely metaphorical in your description of how DS works. Taken literally, each of your statements about DS is wrong.
However, I agree with what I think is your conclusion that in all plausible scenarios there's going to be no measurable performance difference between blueprint and DS.
thanks
david jencks
On Mar 3, 2014, at 11:36 PM, Achim Nierbeck <bc...@googlemail.com> wrote:
> I don't think there are any awailable yet,
> and actually I don't expect there to be much of a difference.
> Both are basically doing the same thing.
> Blueprint does have an extender that will do the wiring for you,
> so there might be a "overhead" on the start of the bundle ...
> but I don't expect there to be an overhead later on, or at least not
> significant.
> DS is just a "convenience-wrapper" for standard OSGi technology.
> During build-time the BND or what ever will transform the annotations to
> Service-Trackers and Service Registrations.
>
> At the end it boils down to services and service-trackers that are
> "hidden" for the user, either by a xml syntax and an extender, or an
> annotation and a build time enhancement.
>
> regards, Achim
>
>
>
> 2014-03-03 22:55 GMT+01:00 asookazian2 <as...@gmail.com>:
> Any info on perf metrics on DS vs. BP? thx.
>
>
>
> --
> View this message in context: http://karaf.922171.n3.nabble.com/performance-metrics-blueprint-vs-declarative-services-in-karaf-3-0-x-tp4032028.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
>
>
> --
>
> Apache Karaf <http://karaf.apache.org/> Committer & PMC
> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead
> blog <http://notizblog.nierbeck.de/>
>
> Software Architect / Project Manager / Scrum Master
>
Re: performance metrics blueprint vs. declarative services in karaf 3.0.x
Posted by Achim Nierbeck <bc...@googlemail.com>.
I don't think there are any awailable yet,
and actually I don't expect there to be much of a difference.
Both are basically doing the same thing.
Blueprint does have an extender that will do the wiring for you,
so there might be a "overhead" on the start of the bundle ...
but I don't expect there to be an overhead later on, or at least not
significant.
DS is just a "convenience-wrapper" for standard OSGi technology.
During build-time the BND or what ever will transform the annotations to
Service-Trackers and Service Registrations.
At the end it boils down to services and service-trackers that are
"hidden" for the user, either by a xml syntax and an extender, or an
annotation and a build time enhancement.
regards, Achim
2014-03-03 22:55 GMT+01:00 asookazian2 <as...@gmail.com>:
> Any info on perf metrics on DS vs. BP? thx.
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/performance-metrics-blueprint-vs-declarative-services-in-karaf-3-0-x-tp4032028.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>
--
Apache Karaf <http://karaf.apache.org/> Committer & PMC
OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer &
Project Lead
blog <http://notizblog.nierbeck.de/>
Software Architect / Project Manager / Scrum Master