Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
M
mariadb
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
mariadb
Commits
64f68462
Commit
64f68462
authored
Jun 05, 2009
by
vasil
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
branches/zip:
Add ChangeLog entry for r5261.
parent
610ad519
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
16 additions
and
0 deletions
+16
-0
ChangeLog
ChangeLog
+16
-0
No files found.
ChangeLog
View file @
64f68462
2009-06-05 The InnoDB Team
* buf/buf0lru.c, buf/buf0rea.c, handler/ha_innodb.cc,
include/srv0srv.h, srv/srv0srv.c:
Fix a bug in linear read ahead:
1) Take into account access pattern when deciding whether or not to
do linear read ahead.
2) Expose a knob innodb_read_ahead_factor = [0-64] default (8),
dynamic, global to control linear read ahead behvior. This is the
value of the number of pages that InnoDB will tolerate within a
64 page extent even if they are accessed out of order or have
not been accessed at all. This number (which varies from 0 to 64)
is indicative of the slack that we have when deciding about linear
readahead.
3) Disable random read ahead. Keep the code for now.
2009-06-03 The InnoDB Team
2009-06-03 The InnoDB Team
* dict/dict0dict.c, mysql-test/t/innodb_mysql.test,
* dict/dict0dict.c, mysql-test/t/innodb_mysql.test,
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment