Flare very slow

[PhilipBogner]

Hey guys,

when we work with flare, it is very slow. The performance of the computer running flare is OK! But if we type some content in flare, we can see how the letters came after and after. If we press the delete button on the keyboard, it takes a while til the letter is deleted. If we hold the delete button, it takes a while and than it jumps very slowly from letter to letter til they are deleted.

Did anybody know what we can do?

[paintedturtle]

The performance of the computer running flare is OK! But if we type some content in flare, we can see how the letters came after and after. If we press the delete button on the keyboard, it takes a while til the letter is deleted. If we hold the delete button, it takes a while and than it jumps very slowly from letter to letter til they are deleted.

That's a big problem! What version of Flare are you running on what OS?

[Robotman]

Hi Philip, are you running projects stored on a networked drive?

[SteveS]

Can you identify when it started happening?

If you haven't done so, reboot the computer.

Things you can do include deleting the analyzer folder and turning off Auto suggestion (File -> Options -> Auto suggestion).

HTH

[PhilipBogner]

Hey,

we're running Flare V11 on Win10.

What we already have done:
Deactivate following settings:
File > Options > XML Editor > Text Rendering options
File > Options > Auto Suggestions
File > General > Auto-Reload Documents

This helps much, but its still not running smoothly.

Yes, we are running the projects on a network drive.

[RamonS]

Yes, we are running the projects on a network drive.

That is not recommended because it is known to drag down performance. Do I assume correctly that you did this all along and did not encounter performance issues of the magnitude you experience now? Also, did the slowness occur after moving to Flare 11 or after moving to Win 10?

I suggest to look into using source control to take over the part of what the network share now does. That way you will work with projects locally and have better control over changes made. With a network share the last one in wins, which sooner or later will overwrite changes made.

[salem16]

Scares me to see you're running Flare 11 with Windows 10. We used Flare 9 for years with Windows 7, and things were smooth. Recently, we tried moving to Flare 12 still with Windows 7, but the problems were many, bringing us to a near standstill. Then we tried Flare 11, and it seemed to behave a bit more acceptably, so we went with it. Boy, each day, it's proving to be more of a mistake. The latest trouble: cannot create/rename folders. Every new folder stays as "NewFolder." MadCap support has sent the usual checklist of questions and things to try, none of which work, and we've got a major deadline looming. Too late to go back to Flare 9, but we were hoping a move to Windows 8.1 or 10 would solve the issues. Now your post puts me on the brink of despair. I've got to get my work done!

[FrankyT]

I am finding Flare 2017 unusably slow at certain locations in my office.

And I do mean unusably slow. I'm talking about half a second's delay between a key press and the UI updating, every time.

The issue is clearly network-related, since there are locations from which it works OK - i.e. Flare is its usual sluggish self but not unusable.

It seems ridiculous that the speed of Flare is network-dependent. What on earth is it using the network constantly for?

[SteveS]

I am finding Flare 2017 unusably slow at certain locations in my office.

And I do mean unusably slow. I'm talking about half a second's delay between a key press and the UI updating, every time.

The issue is clearly network-related, since there are locations from which it works OK - i.e. Flare is its usual sluggish self but not unusable.

It seems ridiculous that the speed of Flare is network-dependent. What on earth is it using the network constantly for?

Flare will be network dependant for project sharing/ multi user considerations. If you want to share projects (and are not using source control) you will need to put it on a netwrok drive.

I'm guessing autosuggestion is operating over the network and you are connecting wirelessly. So autosuggestion is trying to access a network drive to make a suggestion but the network is having smoko.

HTH

[FrankyT]

Flare will be network dependant for project sharing/ multi user considerations. If you want to share projects (and are not using source control) you will need to put it on a netwrok drive.

I'm using source control (thought everybody did these days) and am not sharing the project.

I'm guessing autosuggestion is operating over the network and you are connecting wirelessly. So autosuggestion is trying to access a network drive to make a suggestion but the network is having smoko.

You're guessing wrong I'm afraid Well, half wrong. Autosuggestion isn't operating over a network. The project is on my local hard drive. I am connecting wirelessly, but I wouldn't expect this to affect the speed of access to local files.

I was able to speed things up to an acceptable pace by removing a lot of department-wide variables files that weren't necessary for my project. I can see that autosuggestion had a lot of work to do with so many variables. However, this step was not necessary when I was working from my own desk, so it does seem that Flare is slower in some parts of the building than others, even when I'm doing everything locally.