> 2 solutions.
> 1- I build a mapper that takes String and returns ObjectName
> 2- you build a ObjectName implementation that caches the ObjectName and
> returns the right Object if you pass me exactly the same String.
OK, but it must be a requirement that this mapping be deterministic i.e. when
|Understood now. IMO Juha's solution seems better insulated from changes
|to JMX spec (or implementation for that matter).
I agree, it would also be JDK1.5 poopoo code from SUN immune :)
So this solution has a clear edge.
|Just to be a complete pain - the client would only need ObjectName,
|Ma
Juha-P Lindfors wrote:
>On Sun, 28 Apr 2002, marc fleury wrote:
>
>>Juha for example. By spec must we have
>>Domain1:name1=value1;name2=value2 == Domain1:name2=value2;name1=value1 ???
>>
>>I would imagine so,
>>
>
>
>yes and this is the problem for performance
>
>-- Juha
>
I've been following thi
On Sun, 28 Apr 2002, marc fleury wrote:
> The reason I don't serialize the instance itself is that the client needs to
> know about the ObjectName class then and I don't want to ship all of JMX to
> a client.
>
> are we in sync?
>
> marcf
>
Understood now. IMO Juha's solution seems better in
, April 28, 2002 3:18 PM
|To: Trevor Squires
|Cc: Larry Sanderson; Jboss-Development@Lists. Sourceforge. Net
|Subject: RE: [JBoss-dev] Why is new ObjectName() so slow?
|
|
||Is there *any* way you can get the ObjectName instance to be
||serialised/deserialised in the call?
|
|I serialize a int hash
|Is there *any* way you can get the ObjectName instance to be
|serialised/deserialised in the call?
I serialize a int hash from the "ObjectName". I used to serialize the
string that creates the Objectname, the line that is commented out, all it
does is get the string from a deserialized invocati
On Sun, 28 Apr 2002, marc fleury wrote:
> Oh by the way if someone feels heroic today here is the code from
> JRMPInvoker
>
Ok, let me try a different answer then:
I'm not familiar with the invokers and I've not seen the whole chain for
JRMP so I'll ask a stupid question:
Is there *any* way y
Oh by the way if someone feels heroic today here is the code from
JRMPInvoker
I believe the line that is commented out on the new ObjectName should either
be the one (with cache at the JMX level solution 2 discussed) or should do a
look up on the Registry but with the String as opposed to a int l
|Sorry if I'm just adding noise, but...
|
|It sounds like the biggest problem is that you keep parsing the same string
|into it's canonical form. Can't the jmx server cache the
|canonical names of
|the given ObjectNames? Then, for each new ObjectName(), check the cache,
|and if it doesn't exist,
D]>
Sent: Sunday, April 28, 2002 12:36 PM
Subject: RE: [JBoss-dev] Why is new ObjectName() so slow?
> On Sun, 28 Apr 2002, marc fleury wrote:
>
> > |because an object name contains a set of properties that need to be
> > |parsed and may also be a pattern which needs to be deter
|Right now I need to take a time out on this. Need to finish the inforIT,
|explain our interceptors to EG and then do that finetuning for training
|slides.
You are a young man with his priorities straight, I like that. Definitely
write that informIT article, I bust my ass to give you exposure, t
On Sun, 28 Apr 2002, marc fleury wrote:
>
> 2 solutions.
> 1- I build a mapper that takes String and returns ObjectName
> 2- you build a ObjectName implementation that caches the ObjectName and
> returns the right Object if you pass me exactly the same String.
>
> Come to think of it we probably n
|The question at the moment is, why do you need to create an object name
|per invocation? Is it possible to cache the object names by mapping them
|to *real* identifies as opposed to this property nonsense? (how many
That is what I do today, with the EJB layer. This means however that we
pass th
On Sun, 28 Apr 2002, marc fleury wrote:
> Juha for example. By spec must we have
> Domain1:name1=value1;name2=value2 == Domain1:name2=value2;name1=value1 ???
>
> I would imagine so,
yes and this is the problem for performance
-- Juha
___
Jboss-devel
|I've go a feeling that the order of the properties does not matter, so
|"DefaultDomain:service=XADataSource,name=DefaultDS" would be the
|same object
|as "DefaultDomain:name=DefaultDS,service=XADataSource".
|I think that's whey he has to parse it early.
right, I ask this as well, I don't remembe
On Sun, 28 Apr 2002, Hiram Chirino wrote:
> Using a set of properties to identify an object just seems werid to me.
yes. it's not just wierd, its clearly a poor design choice in this case.
the object name is used as an identifier and therefore needed for lookup.
overloading the identifier to beco
wrong answer trevor,
marcf
|-Original Message-
|From: Trevor Squires [mailto:[EMAIL PROTECTED]]
|Sent: Sunday, April 28, 2002 11:23 AM
|To: marc fleury
|Cc: [EMAIL PROTECTED]; Jboss-Development@Lists. Sourceforge. Net
|Subject: RE: [JBoss-dev] Why is new ObjectName() so slow?
|
|
|On
CTED]>
|>To: marc fleury <[EMAIL PROTECTED]>
|>CC: "Jboss-Development@Lists. Sourceforge. Net"
|><[EMAIL PROTECTED]>
|>Subject: Re: [JBoss-dev] Why is new ObjectName() so slow?
|>Date: Sun, 28 Apr 2002 21:39:26 +0300 (EET DST)
|>
|>
|>because an object
On Sun, 28 Apr 2002, marc fleury wrote:
> |because an object name contains a set of properties that need to be
> |parsed and may also be a pattern which needs to be determined
>
> right the value=name pairs
>
> |the current implementation does this eagerly at object name creation
> |time
>
> can
>From: "marc fleury" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>CC: "Jboss-Development@Lists. Sourceforge. Net"
><[EMAIL PROTECTED]>
>Subject: RE: [JBoss-dev] Why is new ObjectName() so slow?
>Date: Sun, 28 Apr 2002 11:49:46 -0700
>
On Sun, 28 Apr 2002, marc fleury wrote:
> |because an object name contains a set of properties that need to be
> |parsed and may also be a pattern which needs to be determined
>
> right the value=name pairs
Which in a string passed to a constructor are not guaranteed to be
canonical or well for
making the
properties part of the identifier.
Do you know what I mean??
Regards,
Hiram
>From: Juha-P Lindfors <[EMAIL PROTECTED]>
>To: marc fleury <[EMAIL PROTECTED]>
>CC: "Jboss-Development@Lists. Sourceforge. Net"
><[EMAIL PROTECTED]>
>Subject: Re:
|because an object name contains a set of properties that need to be
|parsed and may also be a pattern which needs to be determined
right the value=name pairs
|the current implementation does this eagerly at object name creation
|time
can we do this lazily? can't we build equality and hash on t
because an object name contains a set of properties that need to be
parsed and may also be a pattern which needs to be determined
the current implementation does this eagerly at object name creation
time
-- Juha
On Sun, 28 Apr 2002, marc fleury wrote:
> ok,
>
> I know I asked already and I c
ok,
I know I asked already and I can't remember the reason why creating an
ObjectName should be S slow. Can one of the JMX gurus enlighten me and
explain the reason.
(yes again sorry)
last I remembered the new ObjectName would take half the time of the
invocation (!).
If that is still the
25 matches
Mail list logo