| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> comp.databases.theory -> Re: The TransRelational Model: Performance Concerns
i think the comments below are 'jumping the gun'. i'd like to see a
real implementation before i said similar.
permit me though, to offer a little provocation about something that i've wondered for some years, ever since even little machines could support hundreds of megabytes of fast memory at fairly low cost: i know for a fact that a medium-small airline (say 200 planes) used a real-time reservation database (i use the term 'database' advisedly because it was based on PARS / ACP) that occupied 300 MB on disk. of course there are lots of bigger databases than this, but there are even more that are smaller.
lots of databases use 'cache' as intelligently as they can but with lots of complications and arbitrary heuristics and so forth. wouldn't it be smart to have a database whose native query and update methods were designed to operate solely in memory? except perhaps for an optionally-symchronized log of updates, there would be no 'checkpointing' or similar mechanisms. in fact, such an engine might be able to support dozens or maybe hundreds of concurrent users without all the multi-tasking and storage coordination plumbing that is so common otherwise. of course, one wouldn't choose the same algorithms that are used for disk-based db's, rather ones that would facilitate memory re-use in an elegant way. comparatively speaking there would be almost no seek delay, almost zero latency and so forth. (i'm also intrigued with the potential storage economy of TRM as i've seen others with similar potential.)
i wonder would we be seeing a different world now had the old core memory been as cheap and plentiful as today's.
magoo
hungrylion2004 wrote:
> "Marshall Spight" <mspight_at_dnai.com> wrote in message news:<6dlsd.509091$D%.281045_at_attbi_s51>...
>
>>Fabian Pascal comments on this very thread: >> >>http://www.dbdebunk.com/page/page/1548800.htm >> >>Unfortunately he doesn't actually have anything to say >>except "trust me, it won't be a problem," although he >>does promise a reply from "Steve Tarin, the inventor >>of TRM ... soon." >>
![]() |
![]() |