diff options
| author | Paul Buetow <paul@buetow.org> | 2021-05-14 09:46:46 +0100 |
|---|---|---|
| committer | Paul Buetow <git@mx.buetow.org> | 2021-05-21 05:11:05 +0100 |
| commit | 1b4af08e53f003c9bd3a0376ec7a7b16e4228b48 (patch) | |
| tree | ad7b5b15e7229df03a8d6100b9119741b30c546a /content/md | |
| parent | 48912c9200d86bdcd0d03d7f8beb6c57632e2fdb (diff) | |
ioriot and some new fonts
Diffstat (limited to 'content/md')
| -rw-r--r-- | content/md/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/md/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.md b/content/md/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.md index 5bb5086f..260a0368 100644 --- a/content/md/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.md +++ b/content/md/gemfeed/2018-06-01-realistic-load-testing-with-ioriot-for-linux.md @@ -21,7 +21,7 @@ This text first was published in the german IT-Administrator computer Magazine. I havn't worked on I/O Riot for some time now, but all what is written here is still valid. I am still using I/O Riot to debug I/O issues and pattern once in a while, so by all means the tool is not obsolete yet. The tool even helped to resolve a major production incident at work involving I/O. -I am eagerly looking forward to revamp I/O Riot so that it uses the new BPF Linux capabilities instead of Systemtap. Also, when I wrote I/O Riot initially, I didn't have any experience with the Go programming language yet and therefore I wrote it in C. Once it gets revamped I might consider using Go instead of C as it would spare me from many segmentation faults and headaches during development ;-). I might also just stick to C for plain performance reasons and just refactor the code dealing with concurrency. +I am eagerly looking forward to revamp I/O Riot so that it uses the new BPF Linux capabilities instead of plain old Systemtap (or alternatively: Newer versions of Systemtap can also use BPF as the backend I have learned). Also, when I wrote I/O Riot initially, I didn't have any experience with the Go programming language yet and therefore I wrote it in C. Once it gets revamped I might consider using Go instead of C as it would spare me from many segmentation faults and headaches during development ;-). I might also just stick to C for plain performance reasons and just refactor the code dealing with concurrency. Pleace notice that some of the screenshots show the command "ioreplay" instead of "ioriot". That's because the name has changed after taking those. |