On Sun, 30 Jan 2005 13:56:50 +0100, Andrea Arcangeli <andrea@cpushare.com> wrote:
On Sun, Jan 30, 2005 at 12:26:33AM +0000, Valentino Volonghi wrote:
This works and I've tested it.
Even if you tested it, I doubt you really benchmarked it ;). Likely it was disabled for you (perhaps you forgot setup.py install?)
Yeah, right... That was an 'old' version. And I forgot to fix it.
Transfer rate was 2.3Mbyte/sec. This is very great!
Something is buggy still, since I get the same page duplicated twice, but the performance are already excellent, actually much faster than what I need. And a lot more than 5 times faster, it goes from 7 req per second to 227 req per second, so it's 32 times faster.
Multiplier depends on the page size.
The next bit to stack on top of the above is a timeout parameter, after the timeout the page has to be re-rendered in the _background_, it's enough to attach a deferred to it, that will overwrite the cache after the rendering is complete.
I'm also afraid I should use the flattener on the url before transforming it to a string? Or not?
It's better to use: url.URL.fromContext(ctx).path
This is as fast as using 32 UP systems with the http load balancer, so you're very right that this was the first angle of attack to use ;).
Ehe :). Not bad for a 1 UP system.