2 Replies Latest reply on Nov 6, 2013 1:24 PM by philmodjunk

    offsite network server connection - optimization



      offsite network server connection - optimization


           We are running the FM server in house.  We have inventory databases and fulfillment databases set up for some of our customers.  They log-in, using a FM Pro Client, to our network to access these databases and place fulfillment orders, see past orders, update/add distributor address information and such.  We have, currently, 4 different companies using this service.  We are getting constant complaints of slow connection speeds.  They place an order with the intent of it being a rush, so we are to fulfill it the same day, but we don't see the order come through until it's too late.  They complain that it takes 2-3 minutes just to get to the log-in screen.  Which, as i understand it, it's as soon as they click on the FM shortcut, that then takes them to the screen that would allow them to log into the fulfillment database.  We are considering downloading the databases directly to their computers, so they are working with them locally, then sync them later.  But i'm not sure if that is going to take care of the issue or not.  Any other suggestions?

        • 1. Re: offsite network server connection - optimization

               What speed internet connections is being used on host side and clients side?

               What are you using filemaker pro or filemaker server ?

               You may need a faster server and or internet connections.

               There are also web hosting services available



          • 2. Re: offsite network server connection - optimization

                 Once upon a time, a race horse trainer gave his jockey detailed instructions in how he wanted a horse ridden in order to win the race. Then the race was started and the horse started last, ran last and finished last. The trainer stormed up to the jockey and demanded an explanation as to why he didn't follow the trainer's instructions. The jockey's reply: "Track rules require that I stay on the horse at all times."

                 In your case, the "horse" is the client's internet connection speed. There are design choices you can make to improve added delays in response to user interaction, but you can't improve it to be better than that basic limitation.

                 Things you can do to improve responsiveness:

            1.           Get a fast client machine. iPad and iPhone clients have slower processors and simply cannot process the data from the host as fast as a good lap top or work station.
            3.           Simplify, Simplify, Simplify. Simple straightforward layouts with minimal graphics and no or very little conditional formatting mean less data to transmit from the host machine to the user's.
            5.           Avoid large found sets and large groups of related records. Summary fields, unstored calculations with aggregate functions such as sum and filtered portals can all significantly delay how fast a screen updates due to the need to do a lot of number crunching to produce the data displayed.
            7.           Never, ever use Refresh WIndow [Flush cached joine results] in a script. This step completely re-evaluates all parts of your layout design and current found set and this can result in really major delays with remote hosts and/or iOS clients.

                 And something that you might experiment with:

                 I've never had an opportunity to test this one, but in theory, splitting your database into a data file and an interface file would make it possible to distribute local copies of the interface file that connect to the hosted data file. Such would eliminate the need to transmit some layout specific data such as a graphic on your layout to the client machine. This design approach is often called the Convert to Seperation Model.