1. 25 Jan, 2005 37 commits
  2. 24 Jan, 2005 3 commits
    • unknown's avatar
      Merge mysql.com:/home/kostja/work/mysql-4.1-5787 · 9531db91
      unknown authored
      into mysql.com:/home/kostja/work/mysql-5.0-root
      
      
      vio/viosocket.c:
        Auto merged
      9531db91
    • unknown's avatar
      Merge bk-internal:/home/bk/mysql-4.1 · 4bb1c716
      unknown authored
      into mysql.com:/home/jimw/my/mysql-4.1-clean
      
      
      4bb1c716
    • unknown's avatar
      A fix for Bug#5787 "mysql_stmt_prepare is upto 8 times slower": · dc43c6ea
      unknown authored
      it's crucial to disable Nagle algorithm on client for no-reply commands
      (like mysql_stmt_free) to always work fast.
      Nagle algorithm instructs the sender to buffer (store) data if any 
      unacknowledged data is outstanding and the size of to-send data is less than
      the network segment. It was exactly the case with COM_STMT_CLOSE after 
      COM_STMT_PREPARE, so the client was waiting for Nagle timer to expire or
       for ACK from the server, while the server was holding up ACK because of 
      delayed acknowledgement algorithm.
      The tricky part is that we have been already disabling Nagle 
      algorithm (by setting TCP_NODELAY)
      almost everywhere except Windows (and maybe Netware).
      It is the reason why the bug was repeatable only with Windows client.
      
      
      vio/viosocket.c:
        A fix for Bug#5787 "mysql_stmt_prepare is upto 8 times slower":
        if we disable Nagle algorithm, do it everywhere.
      dc43c6ea