|
|
|
| Re: How to improve graphics usage performance? [message #1714980 is a reply to message #1714969] |
Wed, 18 November 2015 09:36   |
 Camille Letavernier
Messages: 952
Registered: February 2011 |
Senior Member |
|
|
Hi Rolf and Stephen,
I haven't noticed any performance issue in the Mars versions. The only major issue we had was related to the Model Explorer's context menu, but this has been solved before the actual release.
I can't reproduce any of the issues you describe. Do you have some custom plug-ins installed? Since Papyrus is highly customizable, it is very easy to break general performances of the tool when doing some specific customizations (Especially for the Model Explorer's appearance)
You can also try closing the Outline view, which is known to be slow, especially when the diagram has scrollbars, or any other view that seems to update a lot during graphical operations. While the properties view is not extremely fast, it is expected to refresh under 200-300ms (Much less when selecting a similar element, e.g. from Stereotype1 to Stereotype2). However, the actual refresh of the properties view may also happen if all other views have been refreshed. So, if a foreign view is slow, it may prevent the properties view from updating.
Usually, closing all views one by one (starting with the Outline) is a good way to find the responsible
The Model Explorer - to - Diagram synchronization may also be slow, although the performances have improved a lot in the past releases. Do you use it? Does it help to switch it off?
Additionally, errors may prevent refresh operations entirely. In this case, the editors may seem slow because refresh will never happen. So you can check the error log view and see if anything is reported there. Eclipse also reports warnings in this view when the UI is frozen, so these warnings might help to identify the issue.
HTH,
Camille
Camille Letavernier
|
|
|
| Re: How to improve graphics usage performance? [message #1715001 is a reply to message #1714980] |
Wed, 18 November 2015 11:50 |
Ed Willink
Messages: 7655
Registered: July 2009 |
Senior Member |
|
|
<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi<br>
<br>
Xtext has got more reactive to resource changes so it is possible
that if you have significant OCL / ALF / other textual content
then you may be doing many redundant reparses. Could this be your
scenario?<br>
<br>
Regards<br>
<br>
Ed Willink<br>
<br>
<br>
On 18/11/2015 09:36, Camille Letavernier wrote:<br>
</div>
<blockquote cite="mid:n2hgre$a6$1@xxxxxxxxe.org" type="cite">Hi
Rolf and Stephen,
<br>
<br>
<br>
I haven't noticed any performance issue in the Mars versions. The
only major issue we had was related to the Model Explorer's
context menu, but this has been solved before the actual release.
<br>
<br>
I can't reproduce any of the issues you describe. Do you have some
custom plug-ins installed? Since Papyrus is highly customizable,
it is very easy to break general performances of the tool when
doing some specific customizations (Especially for the Model
Explorer's appearance)
<br>
<br>
You can also try closing the Outline view, which is known to be
slow, especially when the diagram has scrollbars, or any other
view that seems to update a lot during graphical operations. While
the properties view is not extremely fast, it is expected to
refresh under 200-300ms (Much less when selecting a similar
element, e.g. from Stereotype1 to Stereotype2). However, the
actual refresh of the properties view may also happen if all other
views have been refreshed. So, if a foreign view is slow, it may
prevent the properties view from updating.
<br>
<br>
Usually, closing all views one by one (starting with the Outline)
is a good way to find the responsible
<br>
<br>
The Model Explorer - to - Diagram synchronization may also be
slow, although the performances have improved a lot in the past
releases. Do you use it? Does it help to switch it off?
<br>
<br>
Additionally, errors may prevent refresh operations entirely. In
this case, the editors may seem slow because refresh will never
happen. So you can check the error log view and see if anything is
reported there. Eclipse also reports warnings in this view when
the UI is frozen, so these warnings might help to identify the
issue.
<br>
<br>
<br>
HTH,
<br>
Camille
<br>
</blockquote>
<br>
</body>
</html>
|
|
|
|
Powered by
FUDForum. Page generated in 0.02914 seconds
] 
Search
Help
Register
Login
Home
