olap4j-devel — olap4j developers
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(15) |
Jun
(11) |
Jul
(5) |
Aug
(6) |
Sep
(5) |
Oct
(16) |
Nov
(2) |
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
|
Mar
(4) |
Apr
(19) |
May
(10) |
Jun
(9) |
Jul
(23) |
Aug
(1) |
Sep
(3) |
Oct
(18) |
Nov
(2) |
Dec
(5) |
| 2011 |
Jan
(6) |
Feb
(14) |
Mar
(26) |
Apr
(8) |
May
(3) |
Jun
(12) |
Jul
(1) |
Aug
(4) |
Sep
(11) |
Oct
(18) |
Nov
(6) |
Dec
(1) |
| 2012 |
Jan
(24) |
Feb
(29) |
Mar
(11) |
Apr
(13) |
May
(1) |
Jun
(15) |
Jul
(4) |
Aug
(2) |
Sep
(5) |
Oct
(9) |
Nov
(7) |
Dec
(9) |
| 2013 |
Jan
(12) |
Feb
(17) |
Mar
|
Apr
|
May
(2) |
Jun
(11) |
Jul
(7) |
Aug
(2) |
Sep
(4) |
Oct
(4) |
Nov
(1) |
Dec
|
| 2014 |
Jan
(4) |
Feb
(1) |
Mar
(4) |
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(3) |
| 2015 |
Jan
(6) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
(19) |
Apr
(29) |
May
(10) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
1
|
2
|
3
|
4
|
5
|
|
6
|
7
|
8
|
9
|
10
(4) |
11
|
12
|
|
13
|
14
|
15
|
16
|
17
|
18
|
19
|
|
20
|
21
|
22
|
23
|
24
|
25
|
26
|
|
27
|
28
|
29
(1) |
30
|
|
|
|
|
From: Julian Hyde <julianhyde@gm...> - 2009-09-29 18:54:21
|
Today I moved the public API from Mondrian into olap4j. It is checked in as the milestone olap4j-0.9.7.277, and you can browse the API of the new Scenario <http://www.olap4j.org/head/api/org/olap4j/Scenario.html>; interface. The Mondrian functionality is about the same as before. The corresponding Mondrian changes are on Mondrian's main line, which means they will hit the streets as part of mondrian-4.0. I can't say yet whether writeback will be a fully supported Mondrian feature or whether it will remain in the current experimental state. But it's ready for Tom and Paul to add writeback support to the PAT interface, whenever they have a moment. By the way, this is the first feature that is available through Mondrian's olap4j API but not through the old native API. The olap4j interface is so elegant, and it didn't make sense to duplicate the effort. If you want examples for how to use the API, see Mondrian's ScenarioTest <http://p4webhost.eigenbase.org:8080/open/mondrian/testsrc/main/mondrian/tes t/ScenarioTest.java> . The changes to the olap4j API came out simple and powerful. They feel about right to me. I would love to hear whether people think that the olap4j would be suitable for other OLAP engines. Julian |
|
From: Christopher André <christopherandre@ho...> - 2009-09-10 20:02:49
|
Exactly what I was looking for! It seems I created my cache for nothing then ;) Thanks a bunch for the information. Cheers ! Chris -------------------------------------------------- From: <olap4j-devel-request@...> Sent: Thursday, September 10, 2009 5:34 PM To: <olap4j-devel@...> Subject: olap4j-devel Digest, Vol 5, Issue 2 > Send olap4j-devel mailing list submissions to > olap4j-devel@... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/olap4j-devel > or, via email, send a message with subject or body 'help' to > olap4j-devel-request@... > > You can reach the person managing the list at > olap4j-devel-owner@... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of olap4j-devel digest..." > > > Today's Topics: > > 1. Re: OLAP4J (Luc Boudreau) > 2. Re: OLAP4J (Julian Hyde) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 10 Sep 2009 10:10:17 -0400 > From: Luc Boudreau <lucboudreau@...> > Subject: Re: [Olap4j-devel] OLAP4J > To: olap4j-devel@... > Message-ID: > <7fc376ee0909100710l7a8e8edbg560574c54d8a4d8b@...> > Content-Type: text/plain; charset="utf-8" > > The collections are stored in memory, yes. They live as long as the > connection object does. > > If I understand right, you want a cache that spans across multiple > connection objects (OlapConnection). This can already be achieved with the > XMLA driver SOAP request cache. It can be activated with a few more > parameters in the connection string. > > connection = (OlapConnection) DriverManager.getConnection( > "jdbc:xmla:Server= > http://example.com/olap/msmdpump.dll"; > + > ";Cache=org.olap4j.driver.xmla.cache.XmlaOlap4jNamedMemoryCache" > + ";Cache.Name=MyNiftyConnectionCache"); > > The cache lives at the static level. It can therefore be shared by using > the > same cache name each time you create a connection. It will cache all HTTP > requests sent at a given URL. More details are available in the Javadoc > > http://olap4j.org/head/api/org/olap4j/driver/xmla/cache/package-summary.html > > Is this what you are looking for? > > _____________________________ > Luc Boudreau > > > 2009/9/10 Christopher Andre <christopherandre@...> > >> (Switching to English so that everybody can understand: I haven't >> translated the beginning though) >> >> Actually, I save a copy of my metadata in memory to avoid contacting the >> server again when I need these information again. >> Are the collections you mention already stored in memory on the client >> side >> once a first populating query has been returned (in which case my cache >> would be useless)? >> Cheers, >> >> Chris >> >> *From:* Luc Boudreau (LinkedIn Messages) <messages-noreply@...> >> *Sent:* Thursday, September 10, 2009 3:32 PM >> *To:* Christopher Andre <christopherandre@...> >> *Subject:* RE: OLAP4J >> >> LinkedIn >> >> *Luc Boudreau* has sent you a message. >> >> *Date:* 9/10/2009 >> >> *Subject:* RE: OLAP4J >> >> Bonjour Chris, >> >> Comme tu as pu le constater, il est tr?s couteux en temps d'ex?cution >> pour >> le driver XMLA de parcourir l'ensemble des m?ta donn?es d'un cube. Pour >> palier ? ce probl?me, nous utilisons des collections initialis?es au >> dernier >> moment possible. Si ton code client parcours l'ensemble des m?ta donn?es, >> et >> donc provoque l'initialisation des collections d'objets, le driver doit >> donc >> cr?er une panoplie de connections HTTP, lesquelles sont tr?s lentes. >> >> Tu fais mention d'un cache de soft references. ? quel endroit cela a-t-il >> am?lior? la performance? Ou s'agit-il seulement d'un gain en espace >> m?moire? >> >> Je pr?f?rerais si nopus poursuivions cette conversation sur la liste des >> d?veloppeurs d'olap4j. olap4j-devel@... >> >> Luc >> >> On 09/10/09 5:54 AM, Christopher Andre wrote: >> -------------------- >> Bonjour Luc, >> >> Je t'?cris car il me semble que tu participes au projet OLAP4J avec >> Julian >> Hyde. >> Je rencontre actuellement un (petit) probl?me de performances avec le >> pilote XML/A d'OLAP4J quand je cherche ? r?cup?rer les m?ta-donn?es de >> mon >> cube ? partir de mon client: il semblerait qu'il y ait un certain nombre >> de >> connections ?tablies ? ce moment-l? vers le serveur pour tout r?cup?rer. >> J'ai contourn? en cr?ant un cache bas? sur des r?f?rences "soft" sur mon >> client (? cause de probl?matiques de m?moire) mais je me demandais si tu >> avais plus de renseignements ? ce propos? >> Merci d'avance pour ton aide. >> Cordialement, >> >> Chris Andr? >> >> View/reply to this >> message<http://www.linkedin.com/e/IhvfmwvgUT-F5L2mfjCx-wpbPUDH5LkCItCB-_6g5rS/mbi/I1421623692_2/>; >> >> Don't want to receive e-mail notifications? Adjust your message >> settings<http://www.linkedin.com/e/IhvfmwvgUT-F5L2mfjCx-wpbPUDH5LkCItCB-_6g5rS/blk/I1421623692_2/s6hJbOYWrSlI/mdp/>; >> . >> >> ? 2009, LinkedIn Corporation >> >> >> ------------------------------------------------------------------------------ >> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 >> 30-Day >> trial. Simplify your report design, integration and deployment - and >> focus >> on >> what you do best, core application coding. Discover what's new with >> Crystal Reports now. http://p.sf.net/sfu/bobj-july >> _______________________________________________ >> olap4j-devel mailing list >> olap4j-devel@... >> https://lists.sourceforge.net/lists/listinfo/olap4j-devel >> >> > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > Message: 2 > Date: Thu, 10 Sep 2009 08:34:08 -0700 > From: "Julian Hyde" <jhyde@...> > Subject: Re: [Olap4j-devel] OLAP4J > To: <olap4j-devel@...> > Message-ID: <23983945C80B4ADEA44D8762B1BEA206@...> > Content-Type: text/plain; charset="iso-8859-1" > > Also note that all of the parameters accepted by the driver are documented > here: > > http://olap4j.org/head/api/org/olap4j/driver/xmla/XmlaOlap4jDriver.html > > Julian > > > _____ > > From: Luc Boudreau [mailto:lucboudreau@...] > Sent: Thursday, September 10, 2009 7:10 AM > To: olap4j-devel@... > Subject: Re: [Olap4j-devel] OLAP4J > > > The collections are stored in memory, yes. They live as long as the > connection object does. > > If I understand right, you want a cache that spans across multiple > connection objects (OlapConnection). This can already be achieved with the > XMLA driver SOAP request cache. It can be activated with a few more > parameters in the connection string. > > connection = (OlapConnection) DriverManager.getConnection( > > "jdbc:xmla:Server=http://example.com/olap/msmdpump.dll"; > + > ";Cache=org.olap4j.driver.xmla.cache.XmlaOlap4jNamedMemoryCache" > + ";Cache.Name=MyNiftyConnectionCache"); > > The cache lives at the static level. It can therefore be shared by using > the > same cache name each time you create a connection. It will cache all HTTP > requests sent at a given URL. More details are available in the Javadoc > > http://olap4j.org/head/api/org/olap4j/driver/xmla/cache/package-summary.html > > Is this what you are looking for? > > _____________________________ > Luc Boudreau > > > > 2009/9/10 Christopher Andre <christopherandre@...> > > > (Switching to English so that everybody can understand: I haven't > translated > the beginning though) > > Actually, I save a copy of my metadata in memory to avoid contacting the > server again when I need these information again. > Are the collections you mention already stored in memory on the client > side > once a first populating query has been returned (in which case my cache > would be useless)? > Cheers, > > Chris > > From: Luc Boudreau <mailto:messages-noreply@...> (LinkedIn > Messages) > Sent: Thursday, September 10, 2009 3:32 PM > To: Christopher <mailto:christopherandre@...> Andre > Subject: RE: OLAP4J > > > > LinkedIn > > > Luc Boudreau has sent you a message. > > Date: 9/10/2009 > > Subject: RE: OLAP4J > > Bonjour Chris, > > Comme tu as pu le constater, il est tr?s couteux en temps d'ex?cution pour > le driver XMLA de parcourir l'ensemble des m?ta donn?es d'un cube. Pour > palier ? ce probl?me, nous utilisons des collections initialis?es au > dernier > moment possible. Si ton code client parcours l'ensemble des m?ta donn?es, > et > donc provoque l'initialisation des collections d'objets, le driver doit > donc > cr?er une panoplie de connections HTTP, lesquelles sont tr?s lentes. > > Tu fais mention d'un cache de soft references. ? quel endroit cela a-t-il > am?lior? la performance? Ou s'agit-il seulement d'un gain en espace > m?moire? > > Je pr?f?rerais si nopus poursuivions cette conversation sur la liste des > d?veloppeurs d'olap4j. olap4j-devel@... > > Luc > > On 09/10/09 5:54 AM, Christopher Andre wrote: > -------------------- > Bonjour Luc, > > Je t'?cris car il me semble que tu participes au projet OLAP4J avec Julian > Hyde. > Je rencontre actuellement un (petit) probl?me de performances avec le > pilote > XML/A d'OLAP4J quand je cherche ? r?cup?rer les m?ta-donn?es de mon cube ? > partir de mon client: il semblerait qu'il y ait un certain nombre de > connections ?tablies ? ce moment-l? vers le serveur pour tout r?cup?rer. > J'ai contourn? en cr?ant un cache bas? sur des r?f?rences "soft" sur mon > client (? cause de probl?matiques de m?moire) mais je me demandais si tu > avais plus de renseignements ? ce propos? > Merci d'avance pour ton aide. > Cordialement, > > Chris Andr? > > View/reply to this message > <http://www.linkedin.com/e/IhvfmwvgUT-F5L2mfjCx-wpbPUDH5LkCItCB-_6g5rS/mbi/I > 1421623692_2/> > > Don't want to receive e-mail notifications? Adjust your message settings > <http://www.linkedin.com/e/IhvfmwvgUT-F5L2mfjCx-wpbPUDH5LkCItCB-_6g5rS/blk/I > 1421623692_2/s6hJbOYWrSlI/mdp/> . > > ? 2009, LinkedIn Corporation > > > ---------------------------------------------------------------------------- > -- > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > olap4j-devel mailing list > olap4j-devel@... > https://lists.sourceforge.net/lists/listinfo/olap4j-devel > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > > ------------------------------ > > _______________________________________________ > olap4j-devel mailing list > olap4j-devel@... > https://lists.sourceforge.net/lists/listinfo/olap4j-devel > > > End of olap4j-devel Digest, Vol 5, Issue 2 > ****************************************** > |
|
From: Julian Hyde <jhyde@pe...> - 2009-09-10 15:34:37
|
Also note that all of the parameters accepted by the driver are documented here: http://olap4j.org/head/api/org/olap4j/driver/xmla/XmlaOlap4jDriver.html Julian _____ From: Luc Boudreau [mailto:lucboudreau@...] Sent: Thursday, September 10, 2009 7:10 AM To: olap4j-devel@... Subject: Re: [Olap4j-devel] OLAP4J The collections are stored in memory, yes. They live as long as the connection object does. If I understand right, you want a cache that spans across multiple connection objects (OlapConnection). This can already be achieved with the XMLA driver SOAP request cache. It can be activated with a few more parameters in the connection string. connection = (OlapConnection) DriverManager.getConnection( "jdbc:xmla:Server=http://example.com/olap/msmdpump.dll"; + ";Cache=org.olap4j.driver.xmla.cache.XmlaOlap4jNamedMemoryCache" + ";Cache.Name=MyNiftyConnectionCache"); The cache lives at the static level. It can therefore be shared by using the same cache name each time you create a connection. It will cache all HTTP requests sent at a given URL. More details are available in the Javadoc http://olap4j.org/head/api/org/olap4j/driver/xmla/cache/package-summary.html Is this what you are looking for? _____________________________ Luc Boudreau 2009/9/10 Christopher Andre <christopherandre@...> (Switching to English so that everybody can understand: I haven't translated the beginning though) Actually, I save a copy of my metadata in memory to avoid contacting the server again when I need these information again. Are the collections you mention already stored in memory on the client side once a first populating query has been returned (in which case my cache would be useless)? Cheers, Chris From: Luc Boudreau <mailto:messages-noreply@...> (LinkedIn Messages) Sent: Thursday, September 10, 2009 3:32 PM To: Christopher <mailto:christopherandre@...> Andre Subject: RE: OLAP4J LinkedIn Luc Boudreau has sent you a message. Date: 9/10/2009 Subject: RE: OLAP4J Bonjour Chris, Comme tu as pu le constater, il est très couteux en temps d'exécution pour le driver XMLA de parcourir l'ensemble des méta données d'un cube. Pour palier à ce problème, nous utilisons des collections initialisées au dernier moment possible. Si ton code client parcours l'ensemble des méta données, et donc provoque l'initialisation des collections d'objets, le driver doit donc créer une panoplie de connections HTTP, lesquelles sont très lentes. Tu fais mention d'un cache de soft references. À quel endroit cela a-t-il amélioré la performance? Ou s'agit-il seulement d'un gain en espace mémoire? Je préfèrerais si nopus poursuivions cette conversation sur la liste des développeurs d'olap4j. olap4j-devel@... Luc On 09/10/09 5:54 AM, Christopher Andre wrote: -------------------- Bonjour Luc, Je t'écris car il me semble que tu participes au projet OLAP4J avec Julian Hyde. Je rencontre actuellement un (petit) problème de performances avec le pilote XML/A d'OLAP4J quand je cherche à récupérer les méta-données de mon cube à partir de mon client: il semblerait qu'il y ait un certain nombre de connections établies à ce moment-là vers le serveur pour tout récupérer. J'ai contourné en créant un cache basé sur des références "soft" sur mon client (à cause de problématiques de mémoire) mais je me demandais si tu avais plus de renseignements à ce propos? Merci d'avance pour ton aide. Cordialement, Chris André View/reply to this message <http://www.linkedin.com/e/IhvfmwvgUT-F5L2mfjCx-wpbPUDH5LkCItCB-_6g5rS/mbi/I 1421623692_2/> Don't want to receive e-mail notifications? Adjust your message settings <http://www.linkedin.com/e/IhvfmwvgUT-F5L2mfjCx-wpbPUDH5LkCItCB-_6g5rS/blk/I 1421623692_2/s6hJbOYWrSlI/mdp/> . © 2009, LinkedIn Corporation ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ olap4j-devel mailing list olap4j-devel@... https://lists.sourceforge.net/lists/listinfo/olap4j-devel |
|
From: Luc Boudreau <lucboudreau@gm...> - 2009-09-10 14:10:47
|
The collections are stored in memory, yes. They live as long as the
connection object does.
If I understand right, you want a cache that spans across multiple
connection objects (OlapConnection). This can already be achieved with the
XMLA driver SOAP request cache. It can be activated with a few more
parameters in the connection string.
connection = (OlapConnection) DriverManager.getConnection(
"jdbc:xmla:Server=
http://example.com/olap/msmdpump.dll";
+
";Cache=org.olap4j.driver.xmla.cache.XmlaOlap4jNamedMemoryCache"
+ ";Cache.Name=MyNiftyConnectionCache");
The cache lives at the static level. It can therefore be shared by using the
same cache name each time you create a connection. It will cache all HTTP
requests sent at a given URL. More details are available in the Javadoc
http://olap4j.org/head/api/org/olap4j/driver/xmla/cache/package-summary.html
Is this what you are looking for?
_____________________________
Luc Boudreau
2009/9/10 Christopher Andre <christopherandre@...>
> (Switching to English so that everybody can understand: I haven't
> translated the beginning though)
>
> Actually, I save a copy of my metadata in memory to avoid contacting the
> server again when I need these information again.
> Are the collections you mention already stored in memory on the client side
> once a first populating query has been returned (in which case my cache
> would be useless)?
> Cheers,
>
> Chris
>
> *From:* Luc Boudreau (LinkedIn Messages) <messages-noreply@...>
> *Sent:* Thursday, September 10, 2009 3:32 PM
> *To:* Christopher Andre <christopherandre@...>
> *Subject:* RE: OLAP4J
>
> LinkedIn
>
> *Luc Boudreau* has sent you a message.
>
> *Date:* 9/10/2009
>
> *Subject:* RE: OLAP4J
>
> Bonjour Chris,
>
> Comme tu as pu le constater, il est très couteux en temps d'exécution pour
> le driver XMLA de parcourir l'ensemble des méta données d'un cube. Pour
> palier à ce problème, nous utilisons des collections initialisées au dernier
> moment possible. Si ton code client parcours l'ensemble des méta données, et
> donc provoque l'initialisation des collections d'objets, le driver doit donc
> créer une panoplie de connections HTTP, lesquelles sont très lentes.
>
> Tu fais mention d'un cache de soft references. À quel endroit cela a-t-il
> amélioré la performance? Ou s'agit-il seulement d'un gain en espace mémoire?
>
> Je préfèrerais si nopus poursuivions cette conversation sur la liste des
> développeurs d'olap4j. olap4j-devel@...
>
> Luc
>
> On 09/10/09 5:54 AM, Christopher Andre wrote:
> --------------------
> Bonjour Luc,
>
> Je t'écris car il me semble que tu participes au projet OLAP4J avec Julian
> Hyde.
> Je rencontre actuellement un (petit) problème de performances avec le
> pilote XML/A d'OLAP4J quand je cherche à récupérer les méta-données de mon
> cube à partir de mon client: il semblerait qu'il y ait un certain nombre de
> connections établies à ce moment-là vers le serveur pour tout récupérer.
> J'ai contourné en créant un cache basé sur des références "soft" sur mon
> client (à cause de problématiques de mémoire) mais je me demandais si tu
> avais plus de renseignements à ce propos?
> Merci d'avance pour ton aide.
> Cordialement,
>
> Chris André
>
> View/reply to this message<http://www.linkedin.com/e/IhvfmwvgUT-F5L2mfjCx-wpbPUDH5LkCItCB-_6g5rS/mbi/I1421623692_2/>;
>
> Don't want to receive e-mail notifications? Adjust your message settings<http://www.linkedin.com/e/IhvfmwvgUT-F5L2mfjCx-wpbPUDH5LkCItCB-_6g5rS/blk/I1421623692_2/s6hJbOYWrSlI/mdp/>;
> .
>
> © 2009, LinkedIn Corporation
>
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus
> on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> olap4j-devel mailing list
> olap4j-devel@...
> https://lists.sourceforge.net/lists/listinfo/olap4j-devel
>
>
|
|
From: Christopher Andre <christopherandre@ho...> - 2009-09-10 14:01:51
|
(Switching to English so that everybody can understand: I haven't translated the beginning though)
Actually, I save a copy of my metadata in memory to avoid contacting the server again when I need these information again.
Are the collections you mention already stored in memory on the client side once a first populating query has been returned (in which case my cache would be useless)?
Cheers,
Chris
From: Luc Boudreau (LinkedIn Messages)
Sent: Thursday, September 10, 2009 3:32 PM
To: Christopher Andre
Subject: RE: OLAP4J
LinkedIn
Luc Boudreau has sent you a message.
Date: 9/10/2009
Subject: RE: OLAP4J
Bonjour Chris,
Comme tu as pu le constater, il est très couteux en temps d'exécution pour le driver XMLA de parcourir l'ensemble des méta données d'un cube. Pour palier à ce problème, nous utilisons des collections initialisées au dernier moment possible. Si ton code client parcours l'ensemble des méta données, et donc provoque l'initialisation des collections d'objets, le driver doit donc créer une panoplie de connections HTTP, lesquelles sont très lentes.
Tu fais mention d'un cache de soft references. À quel endroit cela a-t-il amélioré la performance? Ou s'agit-il seulement d'un gain en espace mémoire?
Je préfèrerais si nopus poursuivions cette conversation sur la liste des développeurs d'olap4j. olap4j-devel@...
Luc
On 09/10/09 5:54 AM, Christopher Andre wrote:
--------------------
Bonjour Luc,
Je t'écris car il me semble que tu participes au projet OLAP4J avec Julian Hyde.
Je rencontre actuellement un (petit) problème de performances avec le pilote XML/A d'OLAP4J quand je cherche à récupérer les méta-données de mon cube à partir de mon client: il semblerait qu'il y ait un certain nombre de connections établies à ce moment-là vers le serveur pour tout récupérer.
J'ai contourné en créant un cache basé sur des références "soft" sur mon client (à cause de problématiques de mémoire) mais je me demandais si tu avais plus de renseignements à ce propos?
Merci d'avance pour ton aide.
Cordialement,
Chris André
View/reply to this message
Don't want to receive e-mail notifications? Adjust your message settings.
© 2009, LinkedIn Corporation
|