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 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 formed. | |> |> |the current implementation does this eagerly at object name creation |> |time |> |> can we do this lazily? can't we build equality and hash on the |FULL string? | |No. ObjectNames are immutable - the only time you have an opportunity to |throw malformed exceptions is at construction time. | |> it strikes that the eager parsing is silly (eats up 50% of the |time !!!) and |> only really useful in querying? Can you think of optimizations? | |50% of *what* time exactly? How many times are you creating the |ObjectName instance? | |Is it (de)serialisation that's causing you the problem? If so, see below. | |> |> It would really be appreciated as it would enable Bill's dream |of the CORBA |> world really working in our JBoss implementation, the fast ON |lookup and bla |> bla bla . |> |> Let me know if you can optimize it, please spend at least 10min thinking |> about it. |> Otherwise it sort of makes the invokers sort of useless at the JMX level. |> |> Any optimization DEEPLY appreciated, this is deep. And you are the man. | |Ok, the only "laziness" that we can insert while still being compliant is |on deserialization. | |Beyond that, consider not using ObjectNames in your invocation layer - |they are great big pigs designed to do too much. | |Trevor _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
