Oracle Community Directory
Oracle Community FAQ
My Oracle Support Community (MOSC)
Go Directly To
Oracle Technology Network Community
My Oracle Support Community
OPN Cloud Connection
Oracle Employee Community
Oracle User Group Community
OTN Speaker Bureau
Berkeley DB Family
Berkeley DB High Availability (Replication)
Please enter a title.
You can not post a blank message. Please type your message and try again.
This discussion is archived
: Apr 19, 2011 7:26 PM by
Why RepMgr waiting a ack costs 40 millsecond
Apr 15, 2011 3:03 AM
OS linux (kernel 2.6.32)
Berkeley DB 5.0.21
Replication group: one master ,one client
When we set Permanent Message Policy=DB_REPMGR_ACKS_ONE, the result out of expection that it costs 40 millsecond for insert 1 record (size <1k).
Who knows the reason? the socket machanism?
This content has been marked as final.
Show 1 reply
Re: Why RepMgr waiting a ack costs 40 millsecond
Apr 19, 2011 7:26 PM
in response to
Now adjust Berkeley Db's source code by setting socket QUICKACK and test again.
We find that waiting for an ack just one millisecond even lower.
Could you tell
what it brings up if I do so
Edited by: user13177882 on 2011-4-19 下午5:25
Edited by: user13177882 on 2011-4-19 下午5:26