diff options
| -rw-r--r-- | open_issues/performance/io_system.mdwn | 9 | ||||
| -rw-r--r-- | topgit.mdwn | 9 |
2 files changed, 16 insertions, 2 deletions
diff --git a/open_issues/performance/io_system.mdwn b/open_issues/performance/io_system.mdwn index f5b5506a..0d41d3c7 100644 --- a/open_issues/performance/io_system.mdwn +++ b/open_issues/performance/io_system.mdwn @@ -33,9 +33,14 @@ 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. -Here's a real use-case: [[binutils_ld_64ksec]]. +Here are some real testcases: + + * [[binutils_ld_64ksec]]; + + * running the Git testsuite which is mostly I/O bound; + + * use [[TopGit]] on a non-toy repository. -Another one is running the Git testsuite which is mostly I/O bound, too. Possible mentors: Samuel Thibault (youpi) diff --git a/topgit.mdwn b/topgit.mdwn index df2b7266..b71038ec 100644 --- a/topgit.mdwn +++ b/topgit.mdwn @@ -25,3 +25,12 @@ License|/fdl]]."]]"""]] We're using this for some packages, where we're maintaining long-lived development branches, for example [[source_repositories/binutils]] or [[source_repositories/glibc]]. The latter one has usage examples, too. + + +# Running it on GNU/Hurd + +Nothing special to that, technically, *only* that our [[I/O system's (non-) +performance|open_issues/performance/io_system]] will render this unbearably +slow for anything but simple test cases. So don't try to run it on the [[GCC]] +or [[glibc]] repositories. Talk to [[tschwinge]] about how he's using it on a +GNU/Linux machine and push the resulting trees to GNU/Hurd systems. |