Serious performance issues saving and simulating.

Peter Giza shared this question 5 years ago
Answered

Why is JIMP such a performance slug? My machine has 32GB RAM, SSDS drives, 3920XM 8 core processor... When I start building up complex templates JIMP becomes nauseatingly slow. Memory consumption never reaches 12GB so I am not resource constrained. CPUs are sleeping for the most part and the K2000 GPU isnt working hard either. Any pointers would be appreciated. The real performance issue is simulation and saving.

Comments (15)

photo
1

Does your prototype have big image files in it?

photo
1

No, but it has a _lot_ of small ones associated with buttons. I have a table that is 11x33 with each cell containing a button with a gradient and an interaction associated with it.So that is 363 buttons with actions.


Pete

photo
1

When you say a table you mean a data master?

photo
1

I'm also having the same performance issues. In my case I use many dynamic panel for I'm trying to prototype a Single Page Application. When I start JIMP it works ok, but soon after I begin to work assigning actions an so, tha app becomes slow even to open the interactions window.

photo
1

Don't waste your time it's a dog

photo
1

Do you mean I better look for other prototype tool? :P


I've already invested about 3 weeks using it :s

photo
1

Oh and did I mention that support is basically nonexistent. Plus there isn't any ability to load an existing css or export one for that matter. Basically just learn twitter bootstrap and you'll be better off or go to irise or...

photo
1

I took a look at Bootstratp but I considered it to be less suitable for "rapid prototyping" but more for sort of "functional prototyping" in terms of time need to achieve the same. That latter needing more time to invest. What do you think?

photo
1

It's ok to critize but please don't lie about support.

photo
1

Victor,


First I'm sorry you have decided to embarrass yourself by calling your customer a liar and doing so in front of all your customers. I certainly hope you are the owner or founder so that you feel immune to further embarrassment.


Second you have just sealed my decision to abandon your platform despite the 8 weeks I've invested into it.


Third with regard to your statement about support, EVERY issue I've submitted to JIMP has met with more questions leading to yet more questions. The turn around time is not less than 24 hours on a good day. Even when I supplied complete examples I never heard from support again. Prove me wrong. There are several other people out there that have the same complaints.


Finally if you decide to rethink your position on customer treatment and satisfaction feel free to reach out. But I can tell having had many years of experience dealing with folks far less patient than myself that you never call your customer a liar - at least not to his/her face or in a public forum.


I wish you the best of luck with JIMP.


Kind regards,


Peter

photo
1

The issue with prototyping is that you end up building what you want. So when you have a prototype that even a css cannot be overlayed or extracted and even perhaps the client bootstrap, the tradeoffs become difficult to differentiate. If I spend 4 weeks prototyping and another 12 weeks developing, I might as well get it done in 8 weeks.


I think that prototyping products need to figure out a median between barebones prototyping and overweight autobloat code.


Of course this is all subject to my personal opinion. I will give JIMP this, it is very easy to learn and it is very good at prototyping individual components and that is why I remained a client up until today after Victor encouraged me to leave with his words of solace.


Pete

photo
1

Hi Peter,


First of all I want to apologize for my last comment. I shouldn't have said that. Having a different opinion about a topic is not an excuse to tell the other part is telling lies. We've been under a lot of pressure these days, getting the next release ready and trying to manage an overwhelming increase of support due to the also increase of customers. That's not an excuse, just an explanation.


Said that, I'm really sorry you are not happy with our support service. I only can find these tickets coming from you in our forum and I believe all of them have been answered:


https://www.justinmind.com/community...


https://www.justinmind.com/community...


https://www.justinmind.com/community...


Again, I apologize if we have caused you any kind of frustration using our tool.

photo
1

As for the main topic in this discussion, there might be some performance issues on pages with lots of events in it. That could happen very easily if you have to copy and paste the same events on a lot of elements. There is a feature planned to be done in the future to define kind of 'master functions' so, along with defining the same thing just in one place it could also fix the performance in those cases. Meanwhile, a workaround is to try to have less events on the same page or split the page in other pages.

photo
1

Victor,


Apology accepted. For what its worth I think that JIMP could be a great tool but having to split things up into tiny bite size pieces just slows the process down. I can see many of the issues as I try to create, copy and paste and then customize. Take a modular approach on components, then if for reasons of performance extend our naming conventions please and then flatten the hierarchy if necessary. Also importing css and java would be a huge help. I would consider adding Twitter bootstrap as part of your templates. As far a learning curve goes JIMP is very easy to catch on. I hope to hear of significant improvements so I can return to the platform at some point.


Regards,


Peter

photo
1

Thanks for your feedback. And stay tuned, we will launch a new version very soon.