05-31-06 06:18 PM
Pascal Bourguignon wrote:
> moi <avk@localhost> writes:
>
>
>
>
> For the enumeration of data-structures, you can make use of your
> imagination, or just read the Table of Contents of any data structure
> text book (or read Moi's answer above, but is it exhaustive?).
I don't think so.
> For the evaluatation of things, here we're considering data structures
> and algorithms, you need to do complexity analysis and obtain an
> expression of the time and space complexities of each case. Note that
> you have to evaluate to a vector:
>
> - space complexities of the data structure,
> - time and space complexities for the (RECENTLY-USED page) operation,
> - time and space complexities for the (GET-LEAST-RECENTLY-USED) operat
ion.
>
> (perhaps also you'll want to consider (ADD-PAGE page) and (REMOVE-PAGE
> page) if the set of page may changes).
Also, the implementation can benefit from hardware support.
[ hardware pageregisters eg have a page-dirty && page-accessed bitty ]
Plus: "usage patterns" ::
* how often is a page referenced, until it finaly drops off ?
* what is the fraction of pages that is actually referenced more than
once, intil it drops off ?
* what is the cost of a read ?
* what is the cost of a write ?
* what is the cost of memory, compared to disk space
* what is the speed of memory (bus), compared to disk ?
* what is the cost of cleverness, compared to bare metal ?
* what is the cost of omitting an item from a bullet list ?
>
> For the comparison, it's rather easy, we'll rely on logic and maths to
> compare the complexities.
>
Ok, I suggest you do the math, Pascal.
I am not good at math.
Moi is only able to make lists :-]
HTH,
AvK
[ Post a follow-up to this message ]
|