Skip to contentSkip to conversation

Combined performance patches update for 2.4.19

DISCUSSION [email protected] 1 participant 1 message Aug 24, 2002 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

Quoting Paolo Ciarrocchi <[email protected]>:

Quoted 6 lines
Quoted 3 lines
Quoted 1 line

note: consoletype[499] exited with preempt_count 1

Yes if you read my FAQ you'd see this is a known issue. I need some higher

help

Quoted 1 line

to sort this out

OK, did you contact Robert Love?

No I don't really want to bother the real developers because they are doing real work. What I'm doing could almost be called butchering, but it definitely gave me a performance advantage and seemed a shame to not share the work given the effort I put in.

Quoted 5 lines
Quoted 3 lines
Quoted 1 line

BTW, thank you for your great work!!

My pleasure, but really the hard work is done by the developers!

Sure, but your "performance" approach is really intersting! Do you use a benchmark?

I don't really have the time to benchmark these things any more than "it feels faster". Really I'm spending way too much time on this as it is and I'm not remotely any authority on what benchmarks to use.

Quoted 4 lines
Quoted 4 lines
Quoted 2 lines

I'm also testing the compressed cache (the patch you've discarded, and I got good performance!)

I'm thinking of eventually merging the latest version of this into 2.4.19

Quoted 8 lines

too

Quoted 1 line

since it can be enabled or disabled. Depends on the demand.

Just an hint ('cause I made some of the test you can see on the compressed cache web page on sourceforge),
if you use that patch boot your box with the
compressed=XXM in order to set the amount of the compressed cache. My box runs fast and happy with 32MiB or 64MiB of compressed cache. My box has 256MiB of Ram.

Ok thanks for the info. I believe the newer cc patch (not in my 2.4.18-ck4) is better anyway. I'm afraid the cc will be later in the piece assuming I can kill off the other bug I've created in the merge. I'd prefer to see a cc patch specifically for 2.4.19 as forward porting it to .19 and then to O(1) (and so on) are just too many steps.

Cheers,
Con Kolivas