diff options
Diffstat (limited to 'bugs/wishlist:_how_does_memory_and_cpu_usage_of_obnam_depend_on_the_number_of_files_and_their_sizes__63__.mdwn')
| -rw-r--r-- | bugs/wishlist:_how_does_memory_and_cpu_usage_of_obnam_depend_on_the_number_of_files_and_their_sizes__63__.mdwn | 17 |
1 files changed, 0 insertions, 17 deletions
diff --git a/bugs/wishlist:_how_does_memory_and_cpu_usage_of_obnam_depend_on_the_number_of_files_and_their_sizes__63__.mdwn b/bugs/wishlist:_how_does_memory_and_cpu_usage_of_obnam_depend_on_the_number_of_files_and_their_sizes__63__.mdwn deleted file mode 100644 index 13215e8..0000000 --- a/bugs/wishlist:_how_does_memory_and_cpu_usage_of_obnam_depend_on_the_number_of_files_and_their_sizes__63__.mdwn +++ /dev/null @@ -1,17 +0,0 @@ -[[!tag obnam-wishlist]] - -As a system administrator I'd like to see data on how the memory and cpu usage of different obnam operations depend on the number of files and their sizes before adopting obnam for my own systems. - -I imagine that in the simplest case you could use something like - - for total_size in 50M 1G 50G 400G 1T 2T 3T; do - for file_size in 1k 2k 4k 8k 16k 32k 1M 64M; do - generate_filesystem $total_size $file_size original/ - /usr/bin/time -f "%e real %P rss" backup original/ backup/ - done - done - -to get cpu and memory usage of backup operations. Repeat same for obnam fsck if you are afraid that its memory usage could depend on total_size or file_size. - -[[done]] A very old wishlist bug. Closing this, since keeping it open -clearly isn't making it happen. --liw |