26 Jan
2010
26 Jan
'10
9:07 p.m.
I do not have a solution, but this is really annoying. In addition to
the time taken by loading Moose, it makes 10 minutes just to check
what are are dependencies Mondrian has.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
26 Jan
26 Jan
10:03 p.m.
On 26 janv. 2010, at 21:07, Alexandre Bergel wrote:
I do not have a solution, but this is really annoying.
In addition to the time taken by loading Moose, it makes 10 minutes just to check what are
are dependencies Mondrian has.
Well, temporary solutions sometimes become less than temporary... I fear this is the
case.
Maybe we can do something with an incremental, on-demand cache: whenever a class or method
is imported, we check whether the cache has been built for it - if not, we built it.
--
Simon
5444
days inactive
5444
days old
1 comments
2 participants
participants (2)
-
Alexandre Bergel -
Simon Denier