Thread View: comp.sys.mac.databases
4 messages
4 total messages
Started by Morris Weinstock
Fri, 08 Jan 1993 16:04
4D Server Memory
Author: Morris Weinstock
Date: Fri, 08 Jan 1993 16:04
Date: Fri, 08 Jan 1993 16:04
5 lines
417 bytes
417 bytes
Does anyone know how much memory the 4D server (for 3 simultaneous users) would take up? Thanks, Morris
Re: 4D Server Memory
Author: Mike Hennahane
Date: Sun, 10 Jan 1993 22:23
Date: Sun, 10 Jan 1993 22:23
13 lines
987 bytes
987 bytes
Morris Weinstock <MAW14@psuvm.psu.edu> writes: >Does anyone know how much memory the 4D server (for 3 simultaneous users) would >take up? this depends on the complexity of the database that it is running. there *is* a downside t giving it too much memory; 4d server has to flush its cache every so often, so if the memory is bumped up high, then the cache will be large and users will have to wait. most databases probably don't need much more than the amount of memory that is the default (i think 1500K). --mike
Re: 4D Server Memory
Author: Ed Estes
Date: Tue, 12 Jan 1993 20:41
Date: Tue, 12 Jan 1993 20:41
36 lines
2018 bytes
2018 bytes
In article <michaelh.726704623@Xenon.Stanford.EDU>, michaelh@Xenon.Stanford.EDU (Mike Hennahane) wrote: > >Morris Weinstock <MAW14@psuvm.psu.edu> writes: > >>Does anyone know how much memory the 4D server (for 3 simultaneous users) would >>take up? > >this depends on the complexity of the database that it is running. >there *is* a downside t giving it too much memory; 4d server has to >flush its cache every so often, so if the memory is bumped up high, >then the cache will be large and users will have to wait. most >databases probably don't need much more than the amount of memory that >is the default (i think 1500K). > >--mike I just got back from DevCon6 (the 4D developer conference) and found out some stuff regarding this... According to Laurent (the author of 4D) the server cache does NOT cause the users to wait. It is a process just like everything else and shares time with other processes. It is the SYSTEM cache that will cause the delays. He recommended a small SYSTEM cache - 32k, and a large 4D server cache. The more memory 4D gets, the better... --Ed --------------------------------------------------------------------------- Ed Estes | "Passion isn't the sole province of those who edestes@pop.nih.gov | write or those who paint, but belongs to those (301) 402-1804 | who love doing what they're doing and are driven "I bleed six colors" | to do it, no matter what." -- unknown ---------------------------------------------------------------------------
Re: 4D Server Memory
Author: SJD9
Date: Wed, 13 Jan 1993 01:35
Date: Wed, 13 Jan 1993 01:35
17 lines
1247 bytes
1247 bytes
>....memory requirements for 4D Server?.... 4D Server requires 1.5 MB, but can benefit from having more. 4D Client (the connecting workstations) also require 1.5 MB. We are currently running a relatively simple 4D db application with 3 users for the better part of every day, and have not had any major problems...in fact, less crashes that with v 2.2.3. For the server we are using a Classic II, with 4 MB RAM, which is also running AppleShare, which is used just lightly. The workstations are hooked via LocalTalk, yet the performance is acceptable. Speed is much improved over v2.2.3 running on the AShare server. Note- this kind of configuration is not recommended by ACI....they recommend a more powerful server, preferably not running any other software. Any other experiences with 4D Server out there? Steve Dahm
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads