Subject | Re: [Firebird-Architect] The biggest RAM database of all... |
---|---|
Author | Jim Starkey |
Post date | 2004-04-05T13:19:56Z |
Marius Popa wrote:
back fill. Indexes and blobs live on disk/page cache, indexes because
nothing is gained, and blobs, well, because they're blobs.
The page generation engine, for which conventional databases have no
analog, is all memory.
Running high volume web sites, the only I/O tends to be logging and
whacks at the word search index.
>it seems jim is right about memory and disksNetfrastructure's model is an in-memory database using the disk as a
>
>http://blog.topix.net/archives/000011.html
>
>"Wade smacked me on the head (gently) and asked why I
>was even thinking about disk anymore. Disk is dead;
>just put the whole thing in RAM and forget about it,
>he said.
>
>
back fill. Indexes and blobs live on disk/page cache, indexes because
nothing is gained, and blobs, well, because they're blobs.
The page generation engine, for which conventional databases have no
analog, is all memory.
Running high volume web sites, the only I/O tends to be logging and
whacks at the word search index.