Project slooooow to open

[jonathanwells]

Hi. Some of my larger projects (190 mb plus) take ages to open. One project takes 1 minute to query the sourcefile (Sourcesafe) and then nearly 3 minutes to finish opening. I am running Flare 6.1.0 on Windows 7. The same project takes about 45 seconds to open in its entirety on a colleagues machine which is a much lower spec but running on Vista. The project also takes quite a long time to close and at the top Flare shows as 'Not responding' during the majority of the closure process. Does anyone have any ideas why I am having such trouble? I have even gone to the extent of uninstalling and reinstalling Flare and this has speeded things up a little, but not by much. Our operations expert says that the CPU is being hammered when the project is opening and memory is only released when Flare is closed, as opposed to when the project is closed. Cheers.

[lacastle]

Your project is probably being scanned by Analyzer (see the status bar at the bottom left corner) when you open the project, which will slow it down a lot. if you don't want that to happen, you can turn off analyzer background scanning.
Here the the flare help topic about analyzer - http://webhelp.madcapsoftware.com/flare ... alyzer.htm

[jonathanwells]

Thanks Laura. I've ticked 'Disable Collecting Phrases' and changed the 'Maximum Word' count to 1 which seems to be the minimum. This has improved it a bit and shaved a minute off the opening time but it's still slow by comparison to my colleages times and he still has the original default setting for analyzer ie. an unticked 'Disable Collecting Phrases' and a 'Maximum Word' count of 30. If anyone else has any ideas I'd be grateful to hear them.

Cheers

[LTinker68]

Sometimes the Analyzer files get corrupted. Close the project in Flare then use Windows Explorer to delete the Analyzer folder. Open the project in Flare -- the Analyzer folder and files will be recreated automatically. It may be slow that first time since Analyzer has to scan the whole project.

[jonathanwells]

Thnaks Ladies, you've shaved 2 minutes off the opening time and I am no longer getting the 'Not Responding' when closing the project.

[jonathanwells]

It's gone back to being slow again and to top it all I have upgarded to 7.1 and it is even worse. It has just taken nearly 6 minutes to open the same project. Can anyone else think of what could be causing the issue please? Closing is much quicker than before so we have made some progress. I just can't understand why it takes so long to open, especially as the same project on my colleagues pc (a lower spec) opens much, much quicker.

[RamonS]

Do you open it locally or from a network share? Are there any significant changes made that Analyzer first has to crunch through? Other possible causes are real-time virus scan (exclude the project folder from scanning), heavily fragmented hard drive (use MyDefrag), lack of RAM, which requires swapping to disk, and other applications running intentionally or unintentionally (virus).

[LTinker68]

And if you just did the upgrade it wouldn't hurt to delete the Analyzer folder. I don't think I had any problems with it when I upgraded but the project I was working on wasn't that big.

[jonathanwells]

Discovered the reason behind this. I was working on a large project and hadn't been closing down my .htm pages (Documents) in my main window after working on them so each time I opened the project, Flare was opening all the old ones. Went to Window > Close All Documents Except This One to close all the pages not in use and now works fine.

[i-tietz]

I once had a problem like that too. The reason then was the open index editor, because Flare scans the project to find the keywords to update the index - and it did that each time I saved a topic ... closing the index editor helped a lot.