Subject 33 Clients hitting an FB Server?
Author Lee Jenkins
Hello all,

We are about to close a deal for a system that would require 33 POS
workstations to be used at one location. Well, the most I've ever seen
is 15 station systems and IB and FB both handle the workload
impressively, especially considering that POS is a high "transaction"
environment.

This particular customer is a high end hotel in on the west coast where
there are several food and retail profit centers (sorry, thats the first
chance I've had to use that term and I wasn't passing it up) that are
located throughout the hotel.

Now, we already have an enterprise level management solution that is
TCP/IP based and while it is intended for use with georgraphically
remote stores, It seems a nice fit this installation. Aggregate data
gets stored on a main server and remoted every night from the remote
"stores". Plus they can connect from anywhere, receive alerts, manage
menus for remote stores, etc.

The thing that I was curious about was IF we didn't have an enterprise
solution or decided NOT to use it, I wonder how well FB would handle
that kind of installation... 33 clients in the restaurant industry
probably means that 15 or less would be used at a given time on average,
but busy times would mean more.

Of course we assume that the DB has been fairly well tuned and indexed
(well as least was well as I have done it :)). The POS stations cache
most of the static data and for the most part, pull very few records and
do not push many back to the server, unless they are running reports
from a POS station.

Personally, I wouldn't think there'd be a problem judging from the
performance I've seen from the largest installs we've done thus far.

BTW, one of the things the customer liked about us (besides our
excellent software :)) was that our software featured a commercial
grade, SQL database server without licensing fees. Most of our
competition still uses desktop databases, lol.
--

Warm Regards,

Lee