Re: Question about Axiom

[email protected] wrote:
>
> It's also worth noting that Linux has several levels of caching - that
> doesn't mean that SQLite's caching is unnecessary either.  At each level,
> there is a cost to doing a transformation when an object is retrieved from
> the database:
>
>  - in Linux
>    - pulling the disk files into memory
>    - translating raw disk data into filesystem data structures
>  - in SQLite
>    - retrieving filesystem data from the kernel
>    - transforming filesystem data into in-memory relational data
> structures
>  - in PySQLite
>    - transforming C data structures into PyObjects
>  - in Axiom
>    - transforming row objects into Axiom item objects
>    - transforming column values into high-level Python attribute values
>
> There are times when avoiding each of these is worthwhile. It's hard to
> measure the exact impact of each independently unless you can turn them
> off one at a time in an actual production system, but anecdotal evidence
> and back-of-the-envelope calculations clearly suggest that each cache does
> play a part in increasing performance.
>

Totally Agreed with you, but in case the total AXIOM storage is bigger
than the RAM, I'm worried about swapping.

AM I correct ?
In which case such "memory full" can occurs ?
Should I defin a "scheduler" to manage the amount of data in the cache ?


Thanks.



-- 
William: http://www.opensource4you.com