Forums Indigo.Design
Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
Close
Infragistics Fan
1935
Indigo Performance
posted

Hi all,

I don't know if you have any performance tips for this situation, but I wanted to share something I've run into with Indigo's performance.

First, here are the specs for my computer and my version of Indigo.

Intel Core i7-3770 @ 3.4 GHz
16 GB Ram
Windows 7 Professional x64 Service Pack 1 (6.1.7601.65536)
Silverlight (5.1.30514.0)
Connection Status: Connected
Indigo Version 4 (Build Dragon.Release_20150116.1 - 4.0.113)

And the specs on the particular project I'm working on are as follows. (1) the open documents at the time, (2) the content of the project in terms of screens, screenparts, etc., and (3) the task manager

    

So as you can see in Task Manager, the app is consuming 881 MB... don't know if that's a whole lot, but for what it does and what's loaded, that seems like a lot.

In any case, there are some stuttering and hanging issues I've run into in several spots in the app.  Mainly it's when I go to close an open document by tapping the X (pictured below), it can at times take 5-7 seconds to close and the app says (Not Responding) up in the left corner of the window.

The other case is when I am running an app, and I have what I'd consider not a particularly complex app, but a screen will take about 2-3 seconds to do a transition from one screen to another when I have NONE set as the transition duration (pictured below).  My guess is that it's prepping the screen that it's returning to, but given my PC's specs, and the size of my Indigo prototype, it doesn't make sense to me that I'd be seeing this kind of stuttering with such a small application.  If I were to model our entire app, it would more than double the number of screens and screenparts.

Any idea what's going on here, or what I might do or look at to improve the performance?

Thanks.

Parents
  • 1075
    posted

    Hi David!

    About the memory usage, Indigo tries to aggressively cache so it might try to reserve quite a lot of memory. However, it should also free it if the system is running low on it, unless there's some other problem (like memory leaks, which have happened before).

    We are not aware of performance issues when closing documents. Do that problem happens immeditely after opening Indigo or do you notice that it degrades after some time of using it?

    What about the other stuttering issues you mention, do they happen as soon as you open Indigo or after you have used it for some time?

    About the time to switch screens on runtime, does this happen while previewing, or while sharing to our servers / dropbox? Would it be possible for you to share that prototype with us (through email to indigo at infragistics.com) so we can review it and see if we can identify any performance bottlenecks?

    Usually, performance is especially affected when you have many screenparts or complex controls (like grids). Of course, 'many' is subjective, and depends on the complexity of the screenparts and how the controls are used too. We don't want you to worry about how many screenparts or which controls do you use, so if we can identify the combinations that cause performance to degrade, it's easier for us to fix those scenarios.

    Regarding performance on design time, some things you can do to improve responsiveness if you have a complex screen are:

    1. Collapse the elements & layers panel.

    2. Collapse the timeline panel.

    3. Disable thumbnails on the interactions explorer view.

    Let us know if you need some guidance in doing any of the above. Again, most of those features are there for a reason, so sometimes disabling them is not practical. However, having a workaround while we try to improve performance for specific usage scenarios might be useful.

    Best regards,

    Santiago.

    Indigo Studio Team.

Reply Children
No Data