🚀 go-pugleaf

> The main problem we're trying to solve is SPEED.  It takes forever to
get into
> the database  (> 10 minutes) since everything is being run across the
network 
> and changing files within the database is also incredibly slow (> 3 minutes).
 
>
> Here's my current suggestions:
>
> 1.) more memory in every machine (4MB in each?)
> 2.) hard drives for the two machines that don't have them (40MB
enough?)
> 3.) different development shell (Easy4D?)
> 4.) different network software?
> 5.) faster CPU's (can't afford)
> 6.) ethernet (can't afford)
> 7.) 4D Compiler (can't afford)
> 8.) 4D Server (can't afford)

First thing to do would be hard drives. You can then put the structures
onto each machine, reducing much of the network traffic. Memory will
also help if the structure is large; also try playing with customizer
and the partitions within 4D.

Don't rule out 4D Server. With the expected upgrade policy, the Server
will cost about $750 :(. A lot of money, but really the easiest solution
to multiuser woes.

There is also a lot that can be done with the database design to help
with multiuser. Avoid automatic relations, so related files aren't searched
and transfered across the network, except when needed. Try copying data
into arrays and using the third party product AreaList to display them
as if they were an output layout.

Good luck,

Michael Schumann

***************************************************************************
             From Planet BMUG, the FirstClass BBS of BMUG, Inc.
              The above message was gatewayed via PostalUnion
***************************************************************************
The message contained in this posting is entirely the poster's personal
opinion.  Any possible, real or perceived, (dis)similarities with the
views held by BMUG, are purely coincidental.
***************************************************************************