[Vm-dev] [Pharo-project] jenkins cog - slow monticello on osx
tudor at tudorgirba.com
Thu Sep 22 17:32:17 UTC 2011
I looked a bit into the slowness of the OS X Jenkins Cog VM with Monticello. The problem exists and it is reproducible.
I performed the following experiments using the following script:
[ 1 to: 100 do: [:x |
| window |
window := MCWorkingCopyBrowser new show.
window delete ] ]
I ran it on the same image using the following vms (on Mac OS X Lion):
- Jenkins VM from 31.08.2011
- Cog VM r2489
I ran the scenario twice with two different setups:
1. I placed the image in an empty folder:
Cog VM 2389: 4808 ms
Jenkins VM: 7345 ms
2. I places the image in a folder that already had a large package-cache with 7400 mcz files:
Cog VM: 4867 ms
Jenkins VM: 50754 ms
- even if there is no package cache, the Jenkins VM seems to perform 1.5 times slower
- when there is a package-cache, it becomes hardly unusable.
On 8 Sep 2011, at 12:10, Tudor Girba wrote:
> I did not forget about this, but I did not have enough time yet.
> On 26 Aug 2011, at 14:40, Igor Stasenko wrote:
>> On 26 August 2011 13:30, Tudor Girba <tudor at tudorgirba.com> wrote:
>>> Since a couple of weeks I am working with the Cog VM built on Jenkins:
>>> Here is a little feedback. It worked quite well, the only problem is that Monticello is really slow in the Moose image. This means that even opening the Monticello Browser takes several seconds.
>>> I thought that this might be induced by something in the Moose image, but if I try with the Elliot's VM (2489), it works blazingly fast.
>> Thanks for the information, Tudor.
>> Apparently the difference between Eliot's VM and Cog-Mac-Cocoa that
>> they are using different frameworks
>> (Carbon vs Cocoa)
>> and i don't know too much details about the difference there.
>> John or Esteban may have better insights how to fix that.
>>> "The coherence of a trip is given by the clearness of the goal."
>> Best regards,
>> Igor Stasenko AKA sig.
> "Yesterday is a fact.
> Tomorrow is a possibility.
> Today is a challenge."
"Sometimes the best solution is not the best solution."
More information about the Vm-dev