NM5 for Mac slows down

[Crescent]

I'd like to have some advice:

NM5 starts to slow down after I copy and paste a map from one file to another. NM5 is painfully slow in case I work with relatively large maps, too. It's so slow that sometimes when entering the branch title the characters are at first missing and later inserted to the end of the branch name.

Background: I use NovaMind 5.2.18 on MacBook Pro (2.3 GHz i5 8GB RAM) running Mac OS X 10.7.3.

Any ideas to run NM5 faster?

[Swiss made]

I notice the same slowdowns in the same circumstances.

[kadso]

" NM5 is painfully slow in case I work with relatively large maps, too"

This happens to me too.  It starts with minor delays then the spinning ball of death arrives. I can send file.

[Crescent]

NovaMind 5.3.4 is a way faster but the same problem occurs in case the mind map is rather large. NM is so slow it's really difficult to enter information fast enough and sometimes the typing error described above occurs.

Any suggestions for solving the problem? How do you handle large maps without slowing down?

[Learning K]

I am busy converting maps from NM4 to NM5.  The maps are link-heavy, but I don't know how you define large.  Often as I am clicking away, it stops and I just sit and wait for it to catch up with itself.

I assume this slowness is from all the hidden code in the layout engine.  I am asking it to do a lot.  I like the finished product.  For me, the wait is not a deal-breaker.  And I don't have the fastest Mac in the west.

But if it did go faster, I would not complain...

[Crescent]

BTW, restarting Novamind helps in case of my problem but it's a temporary solution (works for couple of hours, then another restart is needed). Learning K, you are right about the code of the rendering engine. I hope the developers will fix it in one beautiful day.

[Gideon]

If you have encountered any reproducible slowdown scenarios, please report them to our support team. We're always looking for ways to improve performance, but these things are notoriously difficult to pinpoint...

[aws]

This is definitely a problem that I have noticed for some time.  Right now for review I am using NM5 to mindmap an entire course and the key points and subpoints from 10 chapters.  Before I completed 5 chapters the software was slowing down so that entries fell way behind my typing, and now in the 7th chapter the software is taking so long to respond to returns that I end up typing over entries because it doesn't register the returns to add another point.  Actually this problem existed early with NM5 for even smaller files then seemed to be resolved but is still evident with medium to large files.  If it would help I would be happy to send you the file since I along with many others would like this problem solved.

[olaf_gy]

Hello aws,

which version of NM5 you use, the actual beta? This version has a memory handling problem, I reported already to Support Team. My impression is that this results into the performance issue as well.

[joe.lafferty]

I have exactly the same problem.

I'm running: Version 5.4.8 (5.4.8 (10966)) on 17mbp with latest version of osx ML.

when I type a branch the letters take time to catch up with me, and i was adding branches, and what happened was my typing was too fast.

ended up overwriting the earlier branches.

i've switched off the presenter view and am only editing one mind map

help!

[John A]

Hi,
I, too, have got a bad case of beachball. I have to wait several tens of seconds between any action (sometimes several minutes) and I have had to abandon NM5 and go to the whiteboard as all my work to date is now unusable.
Can we not have an "editing mode" where the graphics and layout logic are a little coarser, with a corresponding increase in speed? Then maybe we can have a "render" button that will implement all the neat graphics and layout logic that makes NM5 so attractive (for the first few hours, anyway)? It appears that the system tries to do nice graphics and layout logic pretty much in real time, essentially locking the User out.
Please - sort this out! I just spent £55 on something that now ... simply ... no ....... longer ............ works.

John