My Rhapsody is VERY slow. I work in a computer with decent configuration (core i3 2120, 8GB ram) but Rhapsody is very slow with "large" (100 class with very little code is large?) projects. I have to wait for Rhapsody for 2 to 4 seconds while it does some misterious actions (roundtrip? code generation? autosave?) with almost EVERY mouse click in interface. Is VERY annoying and counter productive.

I tried to disable roundtrip and auto code generation and its get a little faster, but it still slow.

When I click on some class or object in a diagram or try to open a method from a class, for example, a progress bar appears in status bar and do dozens of "loadings" of misterious things. Every simple action results in the same 2 to 4 seconds wait time.

I don't know what happens, but I think that every time Rhapsody do some "check" in the entire project in every mouse click.

There is some tricks to get Rhapsody running faster with larger projects? Someone else have the same problems?

I discovered a simple trick: it is possible to temporaly unload the packages that you is not working at the time. Right click on the package in the Browser, select Unit and select "unload package". This will help to speed up a little Rhapsody.

However, there are some settings, which can improve performance for huge models (several thousand classes):

* do not set an active component, which has "All Elements" in component scope, use a smaller scope, which aligns to your working area. Elements "In Scope" will be highlighted (bold text) in browser, there is only no code view for elements outside of the current scope,

* unload packages not needed in your context (similar to removing from component scope, but more effect on memory consumption),

* or use "Load on Demand" (model will come up faster, but react slower, when demand loading of additional elements happens),

* do not open a docked feature dialog with the Properties tab enabled AND the View being set to "Filtered By Text", matching property description - this will cause researching within property descriptions on each change of focus in the model.

* avoid referencing external packages in a flat rate mode ("all you can load", e.g. with thousands of optional interfaces of a whole system, while you only need and really use the interfaces of two small subsystems of that system).

Even that your issue sounds different, it might still be of some help.