I seem to remember that the memory footprint was around 5MB for the
virtual engine and that we used up a lot of GDI resources.
If you are in a position to move to OpenROAD (W4GL version 3) you
will be in a much better position in terms of memory, since memory and
performance were two of the prime goals of that release. It also has far
fewer bugs.
---------------------------------------------------------------------
Al Landeck
Ex-Ingres W4GL Engineer, Sustaining Engineering
We are currently using W4gl 2.0 under Windows3.1 on 486/33's with
8-16 MB memory, and 110 MB HD. We have alloted a 10MB permanant
swap file. Our concern is that because our application is very
'frame intensive' i.e., users can have up to 7 - 12 frames open,
and a few of these frames are very 'maths' orientated ( ie,
between 20 - 500 calculations in one go), we may have problems in
the memorey area. Can anyone tell me if Ingres will utilise the Windows
swap file, and if so, how and when does it use it? I'm a bit suspicious
that the WIndows/Ingres/DOS (Whatever) swapfile management is not
up to par. Any advice will be appreciated.
PS. We are implementing Client server, and therefore expect the clients
to do some of the work. Also, my personal opinion is that PCs are crap,
and we have made a decision to move to workstations, but this will take
awhile, so I have to live with what's thrown at me.
Cheers
Mike :)
--
Michael Krey
British Aviation Insurance Group
No one ever got their work done by Friday, except Robinson Crusoe.
3. how difficult from unix/SunOS w4gl tp PC/Windows w4gl
4. SYBASE , DYNAMIC SQL and SQLDA
5. how difficult from unix/SunOS w4gl to PC/Windows w4gl
6. US-TX-AUS-Oracle Sales Specialist
7. Configuration management tools for W4GL
8. OPENXML - How select empty datetime as null?
9. Previewing Ingres reports in ABF/W4GL on PCs
10. Redrawing problem with W4GL on PC
12. PCs, W4GL and W32S - incompatible??
13. "call report" from W4GL 1.0 (PC)