Giter Site home page Giter Site logo

blog's People

Contributors

hugopeixoto avatar tdg5 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

blog's Issues

Unexpected operator

Running the script runs with the following error:

sup2069@debian-pc:~$ sudo sh scripts/dd.obs.test.sh /dev/null
scripts/dd.obs.test.sh: 17: [: -ne: unexpected operator
block size : transfer rate
scripts/dd.obs.test.sh: 37: [: -eq: unexpected operator

When omitting the cache clear (using your website script from 2015, it works). http://blog.tdg5.com/tuning-dd-block-size/

Presently shows optimal bs for the virtual mem "device"

First, thanks for your paper on this; I liked reading it! Actually 'been some time since it was on my TODO list; which happened today --viva summer time :-)

It seems both of your tests are letting the kernel page cache or virtual memory subsystem takes the lead. It's kind of clearer on the "find out optimal input block size", so I'll report here. Apologies for doing so before I could dig in your scripts.

  1. On a fast USB stick (ok fast but)
$ ./dd_ibs_test.sh /media/SDX64_2/dd_ibs_testfile                                                                                                                                                                                    
Generating test file...
block size : transfer rate
     512 : 894 MB/s
    1024 : 1 GB/s
    2048 : 4 GB/s
    4096 : 6 GB/s
    8192 : 5 GB/s
   16384 : 0 GB/s
   32768 : 3 GB/s
   65536 : 2 GB/s
  131072 : 3 GB/s
  262144 : 1 GB/s
  524288 : 1 GB/s
 1048576 : 9 GB/s
 2097152 : 9 GB/s
 4194304 : 7 GB/s
 8388608 : 4 GB/s
16777216 : 0 GB/s
33554432 : 3 GB/s
67108864 : 9 GB/s
  1. On SSD
$ sh $HOME/.local/scripts/dd_ibs_test.sh ~/dd_ibs_testfile                                                                                                                                                                                    
Generating test file...
block size : transfer rate
     512 : 896 MB/s
    1024 : 7 GB/s
    2048 : 0 GB/s
    4096 : 9 GB/s
    8192 : 5 GB/s
   16384 : 9 GB/s
   32768 : 4 GB/s
   65536 : 6 GB/s
  131072 : 8 GB/s
  262144 : 5 GB/s
  524288 : 9 GB/s
 1048576 : 7 GB/s
 2097152 : 8 GB/s
 4194304 : 7 GB/s
 8388608 : 1 GB/s
16777216 : 8 GB/s
33554432 : 5 GB/s
67108864 : 8 GB/s

Test system: Ivy 3.3 GHz with Arch Linux.
Linux llewellyn 4.7.2-1-ck #1 SMP PREEMPT Sat Aug 20 14:07:40 EDT 2016 x86_64 GNU/Linux

Problems with scripts/dd_ibs_test.sh and scripts/dd_obs_test.sh

First, thanks for the handy scripts! Needed to tweak them to make them work though...

Testing this with bash 4.3 on Raspbian, the scripts silently exit without running the tests.

Seems the following line is the problem:
[ -e "$TEST_FILE" ]; TEST_FILE_EXISTS=$?

This test appears to be entirely redundant (and for some reason it causes an early exit as well).

With that, the last line would also simplify from
[ $TEST_FILE_EXISTS -ne 0 ] && rm $TEST_FILE
to
rm $TEST_FILE

Now, I wonder what the purpose of that problematic line above was, exactly? It seems like if a file exists 'ibs' will early exit anyway (with a message), and 'obs' doesn't even have the (working) existence check seen in 'ibs'. Thoughts?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.