[Schevo-devel] Scalability

[Patrick K. O'Brien]

Matthew Scott wrote:
> On 12/7/05, Tom Locke <tom at livelogix.com> wrote:
> 
>>>The important limiting factor in a Durus application may be the
>>>amount of
>>>RAM required by a client.  I think the extra functionality of Schevo
>>>probably requires more RAM, but I don't know how much more, and it
>>>might be difficult to characterize.
>>
>>I assume the whole database doesn't get loaded into ram?
>>
>>Tom
> 
> 
> At first, a Database instance only retrieves information needed to
> initialize Extent instances.
> 
> All other operations, such as the creation of an Entity instance,
> execution of transactions, find operations, etc. retrieve and store
> data as needed from disk in a transactional manner using Durus.

What's a bit unique about Schevo, I think, is that we create class
instances on demand.  We don't actually persist the instances.  So it is
a bit like having our own pickling/unpickling process, which is nice
because we avoid a lot of gotcha's that come with Python pickles.  And
we've got a nice framework for the schema evolution features that we
have in mind (most of which are, unfortunately, still on the todo list
because they depend on everything else we've been doing to date).

-- 
Patrick K. O'Brien
Orbtech       http://www.orbtech.com
Schevo        http://www.schevo.org