On Wed, 30 Jul 2003, Gogulus wrote:
> scott.marlowe wrote:
>
> >On Wed, 30 Jul 2003, Gogulus wrote:
> >
> >
> >
> >>As the clients should be able to work without network connection, they
> >>have to have a local database, and if net connection is on, do the
> >>synchronization with master db. The main idea is, sale cannot stop
> >>because of net connection breakage.
> >>
> >>That's why I am asking if 100 Mhz of CPU, 32 Mbytes of RAM can take care
> >>of a database with around 100 tables, 3-4 of these tables having
> >>50-60000 of records, others have at most 1000.
> >>
> >>
> >
> >I would say yes, but I would also say that you should design this around a
> >character based interface. The overhead of a GUI is gonna make it much
> >slower.
> >
> >I don't know if you're familiar with the ncurses library, but that's what
> >I'd use, along with C or a lightweight scripting language like Perl or
> >PHP.
> >
> >
> Well, the whole application is written in C or C++ after redesign. It
> has to be, because the PC needs to cooperate with a special driver
> handling special hardwares connected to the PC. The GUI is already
> implemented using SVGALib and MicroWin. So I wanna say, not only PGSQL
> will run on it... And it is all on Red Hat 7.1 because of driver limitation.
that's a pretty lightweight environment, so pg should be fine on it. If
the machines start swapping at 32 megs, you may need machines with 64 meg
ram, but that's as big as you should need.
