[Mondrian] Heavy SqlMemberSource.getMemberChildren evaluation

[Sherman Wood]

Once per schema/DB connection, unless as you say, it is aged out of the
JVM.

Sherman

-----Original Message-----
From: mondrian-bounces at pentaho.org [mailto:mondrian-bounces at pentaho.org]
On Behalf Of Peter Tran
Sent: Wednesday, June 03, 2009 9:05 AM
To: Mondrian developer mailing list
Subject: RE: [Mondrian] Heavy SqlMemberSource.getMemberChildren evaluation

Sherman,

It would do this per Mondrian instance right?  If you have several JVMs
with Mondrian running in each, it would do this once per Mondrian JVM.

It's not necessarily cache, but even if it was it may get aged out
depending on the memory allocated for the JVM.

-Peter

-----Original Message-----
From: mondrian-bounces at pentaho.org [mailto:mondrian-bounces at pentaho.org]
On Behalf Of Sherman Wood
Sent: Tuesday, June 02, 2009 5:49 PM
To: 'Mondrian developer mailing list'
Subject: RE: [Mondrian] Heavy SqlMemberSource.getMemberChildren evaluation

It is getting the values for the degenerate dimension. It should only get
this once.

Sherman

-----Original Message-----
From: mondrian-bounces at pentaho.org [mailto:mondrian-bounces at pentaho.org]
On Behalf Of Pedro Alves
Sent: Wednesday, June 03, 2009 5:00 AM
To: Mondrian Mailing List
Subject: [Mondrian] Heavy SqlMemberSource.getMemberChildren evaluation



Hello again.


While implementing agg tables in my dashboards and trying to make this
over 5 billion rows queries light speed, I stumbled upon a very weird
thing


Mondrian is doing the following query:

    2009-06-02 19:49:50,649 DEBUG [mondrian.rolap.RolapUtil]
    SqlMemberSource.getMemberChildren: done executing sql [select
        "blocklist_requests_by_day"."gecko_version" as "c0"
    from
        "blocklist_requests_by_day" as "blocklist_requests_by_day"
    group by
        "blocklist_requests_by_day"."gecko_version"
    order by
        "blocklist_requests_by_day"."gecko_version" ASC
    ], exec+fetch 21993 ms, 425 rows


This is a degenerated dimension, so it's kind'a expected; but the thing is
that I'm not using this dimension in *any* query I'm doing.


Any idea why mondrian is doing this?


Thanks



--
Pedro Alves
pmgalves-at-gmail.com

_______________________________________________
Mondrian mailing list
Mondrian at pentaho.org
http://lists.pentaho.org/mailman/listinfo/mondrian

_______________________________________________
Mondrian mailing list
Mondrian at pentaho.org
http://lists.pentaho.org/mailman/listinfo/mondrian

_______________________________________________
Mondrian mailing list
Mondrian at pentaho.org
http://lists.pentaho.org/mailman/listinfo/mondrian