[FMP-include] with speed?

[Arin]

Okay I know this isn't the most IDEAL setup, but my current project _requires_ it.

I've got several pages that have about 30 [FMP-Include] statements each, which causes the database to perform about 30 "find" requests before returning the results page.

Anyone know any tricks to speed this up?

(Other than the obvious Dual Ghz G4 / P4)

-Arin

[Garry Claridge]

You may be able to cut down on the number of Includes by using IF statements to select records. In the same manner you may be able to use Javascript/Arrays for some selection and reorganising of data.

All the best.

Garry

[Arin]

Thanks Garry,

I think I've already got it narrowed down as far as I can...

I did turn indexing on for about 90% of my fields and that seemed to speed it up a little.

I've been testing on a 266Mhz G3 Powerbook running OS X and FMP 5.5, I'm hoping that once I move the db adn files to the server I'll see _SOME_ speed increase.

[Anatoli]

Don't use Find on fields without index! As the number of records will increase the whole show will stop one day.

[Garry Claridge]

You can try increasing the Cache memory allocation. "Preferences/Application/Memory"

May the speed be with you.

Garry

[scratchmalogicalwax]

Some things to speed up performance most have already been mentioned

Cahche increase by increasing the application memory allocation

Dedicated server - have each server running one application - especially important if running classic Mac OS.

Make sure the server memory is ramped to as much as you can - memory is cheap at the mo' so this should be more affordable - this can be important than processor clock speed (within reason of course!) and dual processor is, I believe, not fully supported by filemaker (I may be out of date on this) so not really worth it on you FMPro client box(es)

Use server in conjunction with your FMPro Unlimited Clients - adds cost but will dramatically improve performance when used in conjunction with WSC and more than one FMPro Unlimited client.

Keep the databases as simple as possible within the constraints of the CGI.

some of this may be out of question because of cost constraints but the point is that a lot can be done to improve performance with a modular system, although it mainly involves distributing the components as much as possible there are also improvements that can be made cheaply such as making sure you never search on non-indexed fields and increasing application memory.

[ April 04, 2002, 01:38 AM: Message edited by: scratchmalogicalwax ]