[Mondrian] RE: Eigenbase perforce change 12887 for review
Julian Hyde
jhyde at pentaho.com
Fri Jun 19 12:49:57 EDT 2009
By the way, we use lists of integers, maps to and from integers, maps to
doubles, all over the code, and in some performance-critical areas. Java
autoboxing makes it easy to forget that every access to these structures
involves converting a primitive type to an object, often allocating an
object for the purpose.
I've been thinking of using apache commons-primitives for these structures.
(See
http://commons.apache.org/primitives/apidocs/org/apache/commons/collections/
primitives/IntList.html for instance.) Anyone have any experience with these
classes? Is it worth the effort?
Julian
> -----Original Message-----
> From: Eric McDermid [mailto:mcdermid at stonecreek.com]
> Sent: Friday, June 19, 2009 9:03 AM
> To: jhyde at pentaho.com
> Cc: 'Mondrian developer mailing list'
> Subject: Re: Eigenbase perforce change 12887 for review
>
> In this case I'm actually porting over something that someone else
> wrote, but my understanding is that it does (at least on the
> data set
> we're using). Since the change was already suggested in the
> original
> code, I didn't spend time characterizing it myself.
>
> On Jun 19, 2009, at 9:55 AM, Julian Hyde wrote:
>
> > Thanks. Did this have a noticeable effect on performance?
> >
> >> From: Eric McDermid [mailto:mcdermid at stonecreek.com]
> >> Sent: Friday, June 19, 2009 7:14 AM
> >> Subject: Eigenbase perforce change 12887 for review
> >>
> >> http://p4web.eigenbase.org/@md=d&c=6PU@//12887?ac=10
> >>
> >> Change 12887 by eric at eric.wednesday.mondrian.dev on
> >> 2009/06/19 07:13:00
> >>
> >> MONDRIAN: Store constrained columns in a map to avoid
> >> iteration in check(), as per suggestion in existing code.
> >
> >
>
>
>
>
More information about the Mondrian
mailing list