Re: (long) Sniffing redo logs to maintain cache consistency?

joel-garry_at_home.com (Joel Garry) wrote in message news:<91884734.0302281643.43d21e23_at_posting.google.com>...
> andrej_at_kintana.com (Andrej Gabara) wrote in message news:<11a3a163.0302280636.2d9ccac4_at_posting.google.com>...
> > In the end, it's not the design with the highest performance that wins. It's
> > the most elegant design that solves critical problems and has acceptable
> > performance. Over time, the thinking of what is acceptable performance
> > changes because cpus run faster and memory gets cheaper.
>
> Most elegant? NOT!
>
> Best marketing? Yes.
>
> Acceptable performance has been < 2 seconds since the 70's.

Sorry, I did not mean acceptable performance actually changes. I meant to say that as cpus get faster and memory gets cheaper, you have more freedom to choose an implementation that still meets "<2sec". One implementation isn't just slower than another because it's a worse design, it's also because of tradeoffs made(performance vs. ease of use).

Also, I'm keeping marketing out of this. I'm just a developer.

Thx
Andrej Received on Sun Mar 02 2003 - 08:47:54 CST