Simon,

You can, more or less, accomplish this already, by setting an
appropriate database cache size for a database file.

This will not eliminate all disk I/O but will ensure that any read
operations are resolved from the cache. The database will still write
page changes to disk as appropriate.

By the way, anecdotal evidence has shown that setting the database cache
to a value of over 5000-8000 pages actually reduces performance.

Finally, there is a fine balance between RAM vs. disk access. As with
anything, in most case being at either end of the spectrum will not have
the best results. Even Microsoft recognized this with SQL Server2000,
and they dropped the ability of the user to specificy which tables which
exist solely in RAM.


Sean
-----Original Message-----
From: simpor81@... [mailto:simpor81@...]
Sent: Wednesday, January 31, 2001 6:38 AM
To: ib-support@yahoogroups.com
Subject: [ib-support] Interbase in the memory (RAM)

Is it possible to make Interbase run in the memory of a machine. From
my knowledge is the writing to the harddrive the thing that takes the
most time. So if you were able to put the hole database in the RAM
then would it be really quick, wouldn't it.

Just a little thought that I have had.

Simon




To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com