jhyde at pentaho.com
Tue May 19 15:59:30 EDT 2009
I don't know if there would be integrity issues if two users were using the
same URL but ended up with different schema objects. Obviously it would be
inefficient: each schema would have its own cache.
The ideal behavior would be for user B to wait if it needs the same schema
that A is currently loading. But if C comes along and wants a different
schema, there should be a very short critical section where the system
figures out that the schema does not exist and needs to be loaded.
Can you please log a bug for this issue?
From: mondrian-bounces at pentaho.org [mailto:mondrian-bounces at pentaho.org] On
Behalf Of Matt Campbell
Sent: Tuesday, May 19, 2009 10:46 AM
To: Mondrian developer mailing list
Subject: [Mondrian] Pool.get()
The static class Pool has .get methods to retrieve RolapSchemas. These
methods are synchronized. Are they synchronized to prevent data integrity
issues that might arise if the same schema was loaded multiple times
We have been running concurrent usage testing and have noticed that when
multiple users all simultaneously begin using the system (each connecting to
different catalogs) that there is a bottleneck as schemas are loaded.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mondrian