Hello,
Is there are recommendations for tune prefetch* parameters (-prefetchDelay, -prefetchFactor <n>, -prefetchNumRecs <n>, -prefetchPriority <n>)? How to know whether it is necessary to change their values?
I suggest that enabling -prefecthDelay and setting -prefetchFactor 100 are simple and sensible. I mentioned in the other thread that I have not seen any downside to either.
Packing the messages fuller will work better if you also set -Mm to a non-default value. -Mm 8192 is a good start.
To monitor the effectiveness look at the number of records per message. You can get that from the _actServer VST. Or you can just look at the ProTop "servers" screen.
Some More Database Performance Knobs
North American PUG Challenge
Richard Banville
I suggest that enabling -prefecthDelay and setting -prefetchFactor 100 are simple and sensible. I mentioned in the other thread that I have not seen any downside to either.
Packing the messages fuller will work better if you also set -Mm to a non-default value. -Mm 8192 is a good start.
To monitor the effectiveness look at the number of records per message. You can get that from the _actServer VST. Or you can just look at the ProTop "servers" screen.
[quote user="George Potemkin"]
Some More Database Performance Knobs
North American PUG Challenge
Richard Banville
pugchallenge.org/.../NEPUG_Performance.pptx
[/quote]
Unfortunately, the slides without author's comments I do not understand (
But thanks anyway, George!
[quote user="ChUIMonster"]
I suggest that enabling -prefecthDelay and setting -prefetchFactor 100 are simple and sensible. I mentioned in the other thread that I have not seen any downside to either.
Packing the messages fuller will work better if you also set -Mm to a non-default value. -Mm 8192 is a good start.
To monitor the effectiveness look at the number of records per message. You can get that from the _actServer VST. Or you can just look at the ProTop "servers" screen.
[/quote]
Thank you, Tom!