Re: teaching a child - console or GUI
From: Maarten Wiltink (maarten_at_kittensandcats.net)
Date: 07/26/04
- Next message: Fons: "Re: DLL with BPC 7.0"
- Previous message: J French: "Re: DLL with BPC 7.0"
- In reply to: J French: "Re: teaching a child - console or GUI"
- Next in thread: J French: "Re: teaching a child - console or GUI"
- Reply: J French: "Re: teaching a child - console or GUI"
- Reply: Bjørge Sæther: "Re: teaching a child - console or GUI"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 26 Jul 2004 15:58:57 +0200
"J French" <erewhon@nowhere.com> wrote in message
news:410508d6.203155268@news.btclick.com...
[...]
> The problem with having huge R/W structures in RAM is that they /must/
> be backed up in case of total power failure
Certainly. Occasional writeback is a complicating factor, but one that
cannot be skipped. So essentially, you still have to consider your
memory image a cache in front of a disk-based system, or make backups.
Both are well-understood technologies.
> R/O is a different matter, but if one has an R/O data warehouse there
> are so many ways of making things faster that the RAM stuff seems ...
> kind of ... peripheral.
All those other ways can be made faster still by doing them in RAM.
It should even be possible to improve upon some by not assuming that
memory is a scarce and costly resource. An index doesn't need to be
tree-based; a hash may be faster (linear instead of logarithmic time,
I think) when you throw more memory at it. You pay for the memory only
once.
Groetjes,
Maarten Wiltink
- Next message: Fons: "Re: DLL with BPC 7.0"
- Previous message: J French: "Re: DLL with BPC 7.0"
- In reply to: J French: "Re: teaching a child - console or GUI"
- Next in thread: J French: "Re: teaching a child - console or GUI"
- Reply: J French: "Re: teaching a child - console or GUI"
- Reply: Bjørge Sæther: "Re: teaching a child - console or GUI"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|