diff options
Diffstat (limited to 'community/gsoc')
| -rw-r--r-- | community/gsoc/project_ideas/disk_io_performance.mdwn | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/community/gsoc/project_ideas/disk_io_performance.mdwn b/community/gsoc/project_ideas/disk_io_performance.mdwn index 0d793845..dafe2526 100644 --- a/community/gsoc/project_ideas/disk_io_performance.mdwn +++ b/community/gsoc/project_ideas/disk_io_performance.mdwn @@ -21,7 +21,7 @@ The reason for this slowness is lack and/or bad implementation of common 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|service_solahart_jakarta_selatan__082122541663/performance/io_system/clustered_page_faults]]; and -[[open_issues/performance/io_system/read-ahead]]. The +[[service_solahart_jakarta_selatan__082122541663/performance/io_system/read-ahead]]. The [[ext2_filesystem_server|hurd/translator/ext2fs]] might also need some optimizations at a higher logical level. @@ -31,7 +31,7 @@ requires understanding the data flow through the various layers involved in disk access on the Hurd ([[filesystem|hurd/virtual_file_system]], [[pager|hurd/libpager]], driver), and general experience with optimizing complex systems. That said, the killing feature we are definitely -missing is the [[open_issues/performance/io_system/read-ahead]], and even a very simple implementation would bring +missing is the [[service_solahart_jakarta_selatan__082122541663/performance/io_system/read-ahead]], and even a very simple implementation would bring very big performance speedups. Here are some real testcases: |