Skip to main content
tk5121-Visitor
1-Visitor
Apr 18, 2018 7:30 AM UTC
Question

Thingworx Composer is slow

We're using ThingWorx 8.2 and our developers are complaining that the Composer web UI is very slow, even on relatively fast computers. I tested this myself and it was fast until about 30 minutes into editing mashups, when it becomes quite slow (often eventually taking 1-2 seconds to click a button, sometimes more).

 

I see that Chrome memory usage is very high and the web app itself seems very inefficient. I see that a potentially big problem with ThingWorx - as it keeps our developers from being productive. We tested on a MacBook Pro with 16GB memory (both Chrome, Safari), a Macbook Air, and also a powerful Windows PC with 64GB of memory in 3 different browsers including IE.  In all cases, it turned out ThingWorx Composer eventually gets slow.

 

It is of course driving our developers mad.  Is there a remedy for this - or is it just that ThingWorx web interface is old and clunky by nature?

    12 replies

    CarlesColl1-Visitor
    1-Visitor
    Apr 18, 2018 12:32 PM UTC

    You use the new composer or the old composer? I've been using it (Old Composer) for 3 years and I don't have the problem, of course if the mashup you are dealing of it's complex yes it will kill Composer performance.

    Translate
    tk5121-VisitorAuthor
    1-Visitor
    Apr 18, 2018 12:34 PM UTC

    @CarlesColl - we're using the new one.  This happens the more complex a mashup gets, so yes. But I still wouldn't call the mashups very complex, to be honest. I suppose this is just something we'll get used to then, but it does look like we'll need to evaluate possibly other platforms similar to Thingworx.

    Translate
    CarlesColl1-Visitor
    1-Visitor
    Apr 18, 2018 12:50 PM UTC

    We are happy with old composer performance, of course always can be better, and sometimes you need to refresh the browser (but after hours - or days - I never restart my computer ). Just one appointment, I had problems with some Chrome plugins (a way back) and I use a dedicate Chrome session for ThingWorx development.

     

    When Mashups gets complex the best approach it's to cut in pieces.

    Translate
    drichter1-Visitor
    1-Visitor
    Apr 18, 2018 1:23 PM UTC

    We have the same issus. First my computer has 8GB memory. After one or two hours of working with the old composer its become very slow so I close the browser and reopen it. Than I get an upgrade to 16GB an its work a little bit better. The memory upgrade seems not so efficient because the browser (firefox) is limit and use (I think) maximum 4 GB.

    So at the moment I show the mashups in chrome and do my composer stuff with firefox. That has the advantage that the refreshing of the frontend doesn't blog the composer.

    Translate
    Terms & ConditionsAccessibility statement