summaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas/disk_io_performance.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <thomas@schwinge.name>2010-03-28 21:48:46 +0200
committerThomas Schwinge <thomas@schwinge.name>2010-03-28 21:48:46 +0200
commit4b35fc7bdd7ab723cb3db8e9122ed08d996f33b4 (patch)
treee4bb2ffadd136ab05b8abc3c0fa9f305f8c360fe /community/gsoc/project_ideas/disk_io_performance.mdwn
parent34794c7002f679ab9c2d076284ff58288224c47d (diff)
parent96611f76b833159bafeab3443229dfa690178d92 (diff)
Merge commit '96611f76b833159bafeab3443229dfa690178d92' into master-news_next
Conflicts: news/2010-03-31.mdwn
Diffstat (limited to 'community/gsoc/project_ideas/disk_io_performance.mdwn')
-rw-r--r--community/gsoc/project_ideas/disk_io_performance.mdwn12
1 files changed, 6 insertions, 6 deletions
diff --git a/community/gsoc/project_ideas/disk_io_performance.mdwn b/community/gsoc/project_ideas/disk_io_performance.mdwn
index bb047308..b6c857b0 100644
--- a/community/gsoc/project_ideas/disk_io_performance.mdwn
+++ b/community/gsoc/project_ideas/disk_io_performance.mdwn
@@ -11,21 +11,21 @@ is included in the section entitled
[[!meta title="Disk I/O Performance Tuning"]]
The most obvious reason for the Hurd feeling slow compared to mainstream
-systems like GNU/Linux, is very slow harddisk access.
+systems like GNU/Linux, is very slow hard disk access.
The reason for this slowness is lack and/or bad implementation of common
-optimisation techniques, like scheduling reads and writes to minimalize head
+optimization techniques, like scheduling reads and writes to minimize head
movement; effective block caching; effective reads/writes to partial blocks;
reading/writing multiple blocks at once; and read-ahead. The
[[ext2_filesystem_server|hurd/translator/ext2fs]] might also need some
-optimisations at a higher logical level.
+optimizations at a higher logical level.
The goal of this project is to analyze the current situation, and implement/fix
-various optimisations, to achieve significantly better disk performance. It
+various optimizations, to achieve significantly better disk performance. It
requires understanding the data flow through the various layers involved in
-disk acces on the Hurd ([[filesystem|hurd/virtual_file_system]],
+disk access on the Hurd ([[filesystem|hurd/virtual_file_system]],
[[pager|hurd/libpager]], driver), and general experience with
-optimising complex systems. That said, the killing feature we are definitely
+optimizing complex systems. That said, the killing feature we are definitely
missing is the read-ahead, and even a very simple implementation would bring
very big performance speedups.