You're write, it just do it once.

2009/12/4 Cyrille Delaunay <cy.delaunay@gmail.com>
No. But now I just re-execute and it works normally (without package cache) . I will try on a new fresh downloaded image.


2009/12/4 Tudor Girba <tudor.girba@gmail.com>
Hmm,

I do not have that. The cache is built only once. Did you move the image or removed the package-cache folder by any chance?

Cheers,
Doru


On 4 Dec 2009, at 15:32, Cyrille Delaunay wrote:

No, I think it should certainly be that. Now, the problem is that this package cache isn't build only once. If you try to execute this code several times, you will obtain the same result.
Sometimes I don't get the package cache construction but I don't know why. Maybe there is something specific to do.

2009/12/4 Tudor Girba <tudor.girba@gmail.com>
Hi Cyrille,

This is not really a problem, it was a solution for accelerating larger imports, if I understand correctly. Actually, I am not sure why it is needed, but Simon spent time on this. The package cache is built only once, and afterwards you get the loading faster.

Or did I get the problem wrong?

Cheers,
Doru



On 4 Dec 2009, at 15:09, Cyrille Delaunay wrote:

I just opened an issue about my problem
http://code.google.com/p/moose-technology/issues/detail?id=248
:
Try to evaluate this: | mooseModel importer selectedPackages | selectedPackages := {'Fame'}. "we create the moose model" mooseModel := MooseModel new. "we create the importer" importer := MooseSqueakClassPackageImporterTask new. "we set all the importation parameters to the importer" importer model: mooseModel; addFromPackagesNamed: selectedPackages; runWithProgress This will display a progress bar telling that a package cache is being built for a lot (to much) of classes.

2009/12/3 Cyrille Delaunay <cy.delaunay@gmail.com>
ho, Ok:)
But now  I know why it was so long: I think I was importing all Pharo classes. But I don't why. Now it works well, but I still don't know why .
I 'm having a look at it.
Thank you

2009/12/3 Tudor Girba <tudor.girba@gmail.com>
I meant: did you use a profiler to see where the performance problem is :)?

Doru



On 3 Dec 2009, at 13:01, Cyrille Delaunay wrote:

No, normally I havn't  touched to the code concerning the MooseModel creation.

2009/12/3 Tudor Girba <tudor.girba@gmail.com>
Did you try to profile it?

Cheers,
Doru



On 3 Dec 2009, at 12:47, Cyrille Delaunay wrote:

For example you can run the method
      MooseModel class >> mseExportationTest

I remember that some times ago ( some weeks) it was not as long as that. Is it normal ? Am I doing something wrong ?
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Problem solving efficiency grows with the abstractness level of problem understanding."



_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"It's not what we do that matters most, it's how we do it."


_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev


_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Live like you mean it."


_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"One cannot do more than one can do."




_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev