Fast way to extract lines from a large file with 80 billion lines2019 Community Moderator Election“Multipass” scripted modification of large file in-place (file-system level)?Easy way to copy lines from one file to anotherExtract several lines from large text fileHow to group values based on a “connectedness” metric?Print each line multiple but different timesextracting lines of text from a long fileExtracting time from text filefast ways of removing beginning lines from large text fileExtract lines that have a specific ending and use those to extract from another fileWhy does head; tail on a large file sometimes take a long time and sometimes not?

Does fire aspect on a sword, destroy mob drops?

Would mining huge amounts of resources on the Moon change its orbit?

Is "inadequate referencing" a euphemism for plagiarism?

Determine voltage drop over 10G resistors with cheap multimeter

How do hiring committees for research positions view getting "scooped"?

Don't understand why (5 | -2) > 0 is False where (5 or -2) > 0 is True

How to test the sharpness of a knife?

Do I need an EFI partition for each 18.04 ubuntu I have on my HD?

Why doesn't the fusion process of the sun speed up?

How to find the largest number(s) in a list of elements?

label a part of commutative diagram

Norwegian Refugee travel document

Is there any common country to visit for uk and schengen visa?

Air travel with refrigerated insulin

How to balance a monster modification (zombie)?

Animating wave motion in water

Error in master's thesis, I do not know what to do

Writing in a Christian voice

Did Nintendo change its mind about 68000 SNES?

Why doesn't the chatan sign the ketubah?

How can I query the supported timezones in Apex?

Inhabiting Mars versus going straight for a Dyson swarm

How much propellant is used up until liftoff?

What is it called when someone votes for an option that's not their first choice?



Fast way to extract lines from a large file with 80 billion lines



2019 Community Moderator Election“Multipass” scripted modification of large file in-place (file-system level)?Easy way to copy lines from one file to anotherExtract several lines from large text fileHow to group values based on a “connectedness” metric?Print each line multiple but different timesextracting lines of text from a long fileExtracting time from text filefast ways of removing beginning lines from large text fileExtract lines that have a specific ending and use those to extract from another fileWhy does head; tail on a large file sometimes take a long time and sometimes not?










3















I have a large file with 80 billion lines. Now I want to extract a few lines (around 10000) which I know the line number, what is the fastest way to deal with it. Your help is really appreciated



Is it possible to extract those lines from using another file which contains the line numbers? The line numbers in the file of line numbers would not always be consecutive.



For example, the original file is:



0.1
0.2
0.3
0.4
...


the line number file:



1
3
4


the output:



0.1
0.3
0.4









share|improve this question
























  • If you expect to have to do this more than once, consider putting the lines into an SQL database or something of the sort.

    – Nate Eldredge
    Mar 14 at 3:36











  • Are they sequential 10000 lines or sporadic throughout the log file? If sequential and there's some unique pattern at the beginning you could just use grep -A 10000 <pattern> <filename>.

    – kevlinux
    Mar 14 at 3:48






  • 2





    Are line numbers in line number file sorted?

    – JohnKoch
    Mar 14 at 7:54






  • 2





    Are the lines expected to be extracted in the order of the line numbers in the smaller file?

    – Kusalananda
    Mar 14 at 8:03






  • 1





    This might help: stackoverflow.com/questions/6022384/…

    – kevlinux
    Mar 15 at 6:08















3















I have a large file with 80 billion lines. Now I want to extract a few lines (around 10000) which I know the line number, what is the fastest way to deal with it. Your help is really appreciated



Is it possible to extract those lines from using another file which contains the line numbers? The line numbers in the file of line numbers would not always be consecutive.



For example, the original file is:



0.1
0.2
0.3
0.4
...


the line number file:



1
3
4


the output:



0.1
0.3
0.4









share|improve this question
























  • If you expect to have to do this more than once, consider putting the lines into an SQL database or something of the sort.

    – Nate Eldredge
    Mar 14 at 3:36











  • Are they sequential 10000 lines or sporadic throughout the log file? If sequential and there's some unique pattern at the beginning you could just use grep -A 10000 <pattern> <filename>.

    – kevlinux
    Mar 14 at 3:48






  • 2





    Are line numbers in line number file sorted?

    – JohnKoch
    Mar 14 at 7:54






  • 2





    Are the lines expected to be extracted in the order of the line numbers in the smaller file?

    – Kusalananda
    Mar 14 at 8:03






  • 1





    This might help: stackoverflow.com/questions/6022384/…

    – kevlinux
    Mar 15 at 6:08













3












3








3








I have a large file with 80 billion lines. Now I want to extract a few lines (around 10000) which I know the line number, what is the fastest way to deal with it. Your help is really appreciated



Is it possible to extract those lines from using another file which contains the line numbers? The line numbers in the file of line numbers would not always be consecutive.



For example, the original file is:



0.1
0.2
0.3
0.4
...


the line number file:



1
3
4


the output:



0.1
0.3
0.4









share|improve this question
















I have a large file with 80 billion lines. Now I want to extract a few lines (around 10000) which I know the line number, what is the fastest way to deal with it. Your help is really appreciated



Is it possible to extract those lines from using another file which contains the line numbers? The line numbers in the file of line numbers would not always be consecutive.



For example, the original file is:



0.1
0.2
0.3
0.4
...


the line number file:



1
3
4


the output:



0.1
0.3
0.4






linux large-files






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 14 at 8:38









Kusalananda

136k17257425




136k17257425










asked Mar 14 at 3:28









user2842390user2842390

183




183












  • If you expect to have to do this more than once, consider putting the lines into an SQL database or something of the sort.

    – Nate Eldredge
    Mar 14 at 3:36











  • Are they sequential 10000 lines or sporadic throughout the log file? If sequential and there's some unique pattern at the beginning you could just use grep -A 10000 <pattern> <filename>.

    – kevlinux
    Mar 14 at 3:48






  • 2





    Are line numbers in line number file sorted?

    – JohnKoch
    Mar 14 at 7:54






  • 2





    Are the lines expected to be extracted in the order of the line numbers in the smaller file?

    – Kusalananda
    Mar 14 at 8:03






  • 1





    This might help: stackoverflow.com/questions/6022384/…

    – kevlinux
    Mar 15 at 6:08

















  • If you expect to have to do this more than once, consider putting the lines into an SQL database or something of the sort.

    – Nate Eldredge
    Mar 14 at 3:36











  • Are they sequential 10000 lines or sporadic throughout the log file? If sequential and there's some unique pattern at the beginning you could just use grep -A 10000 <pattern> <filename>.

    – kevlinux
    Mar 14 at 3:48






  • 2





    Are line numbers in line number file sorted?

    – JohnKoch
    Mar 14 at 7:54






  • 2





    Are the lines expected to be extracted in the order of the line numbers in the smaller file?

    – Kusalananda
    Mar 14 at 8:03






  • 1





    This might help: stackoverflow.com/questions/6022384/…

    – kevlinux
    Mar 15 at 6:08
















If you expect to have to do this more than once, consider putting the lines into an SQL database or something of the sort.

– Nate Eldredge
Mar 14 at 3:36





If you expect to have to do this more than once, consider putting the lines into an SQL database or something of the sort.

– Nate Eldredge
Mar 14 at 3:36













Are they sequential 10000 lines or sporadic throughout the log file? If sequential and there's some unique pattern at the beginning you could just use grep -A 10000 <pattern> <filename>.

– kevlinux
Mar 14 at 3:48





Are they sequential 10000 lines or sporadic throughout the log file? If sequential and there's some unique pattern at the beginning you could just use grep -A 10000 <pattern> <filename>.

– kevlinux
Mar 14 at 3:48




2




2





Are line numbers in line number file sorted?

– JohnKoch
Mar 14 at 7:54





Are line numbers in line number file sorted?

– JohnKoch
Mar 14 at 7:54




2




2





Are the lines expected to be extracted in the order of the line numbers in the smaller file?

– Kusalananda
Mar 14 at 8:03





Are the lines expected to be extracted in the order of the line numbers in the smaller file?

– Kusalananda
Mar 14 at 8:03




1




1





This might help: stackoverflow.com/questions/6022384/…

– kevlinux
Mar 15 at 6:08





This might help: stackoverflow.com/questions/6022384/…

– kevlinux
Mar 15 at 6:08










4 Answers
4






active

oldest

votes


















2














One liner, using sed:



sed -nf <(sed 's/$/p/' linenumberfile) contentfile


To keep the original order in linenumberfile, you can do



sed -nf <(sed 's/$/p/' linenumberfile) contentfile | paste <(nl linenumberfile | sort -n -k 2,2) - | sort -n -k 1,1 | cut -f 3-


Explanation:



sed 's/$/p/' linenumberfile


generates a sed script which prints the specified line. The script is then fed into another sed (with -n to suppress default printing of the pattern space) to do the actual printing. Since sed process the content file line by line, the output will be in the same order as in the content file. Note that this is a one-pass process so I would expect the speed to be acceptable.



To accelerate the process, one can change p to p;b and add a q at the end of the generated sed script.



To retain the order of the lines as they are in the line number file, nl is used to add "line numbers" to the line number file. So a line number file



4
5
2


would become



1 4
2 5
3 2


The first column records the original order in the line number file.



The file with "line numbers" is then sorted and pasted to the output of sed, to make



3 2 content_of_line2
1 4 content_of_line4
2 5 content_of_line5


then it is sorted using the 1st column as the key, to finally obtain



1 4 content_of_line4
2 5 content_of_line5
3 2 content_of_line2


Finally, cut is used to remove the 2 extra columns.



Benchmarking



It seems sed would do best for a few lines, but perl is the way to go for 10000 lines as specified in the question.



$ cat /proc/cpuinfo | grep -A 4 -m 1 processor
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 60
model name : Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz

$ wc -l linenumber
10 linenumber

$ wc -l content
8982457 content

$ file content
content: ASCII text

$ time bash -c "sed -nf <(sed 's/$/p/' linenumber) content > /dev/null"
real 0m0.791s
user 0m0.661s
sys 0m0.133s

$ time bash -c "awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' linenumber content > /dev/null"
real 0m3.061s
user 0m2.908s
sys 0m0.152s

$ time bash -c "./ln.pl linenumber content > /dev/null"
real 0m1.706s
user 0m1.582s
sys 0m0.124s

$ ./genlinenumber.py 100 > linenumber
$ wc -l linenumber
100 linenumber

$ time bash -c "sed -nf <(sed 's/$/p/' linenumber) content > /dev/null"
real 0m3.326s
user 0m3.164s
sys 0m0.164s

$ time bash -c "awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' linenumber content > /dev/null"
real 0m3.055s
user 0m2.890s
sys 0m0.164s

$ time bash -c "./ln.pl linenumber content > /dev/null"
real 0m1.769s
user 0m1.604s
sys 0m0.165s


If it is required to retain the order of lines, the command after the first | can still be used since the time is negligible.



$ ./genlinenumber.py 10000 > linenumber
$ wc -l linenumber
10000 linenumber

$ time bash -c "./ln.pl linenumber content > extract"
real 0m1.933s
user 0m1.791s
sys 0m0.141s

$ time bash -c "paste <(nl linenumber | sort -n -k 2,2) extract | sort -n -k 1,1 | cut -f 3- > /dev/null"
real 0m0.018s
user 0m0.012s
sys 0m0.005s





share|improve this answer




















  • 1





    Done. Suggestions are welcome.

    – Weijun Zhou
    Mar 14 at 8:58











  • Do common versions of sed support line numbers larger than 32 bits?

    – Nate Eldredge
    Mar 14 at 14:40






  • 1





    You are right. I made a mistake in last edits.

    – Weijun Zhou
    Mar 14 at 20:22











  • @NateEldredge I'm not sure about that.

    – Weijun Zhou
    Mar 15 at 0:01


















1














I would use a perl script for this. I came up with this:



#!/usr/bin/perl

# usage: thisscript linenumberslist.txt contentsfile

unless (open(IN, $ARGV[0]))
die "Can't open list of line numbers file '$ARGV[0]'n";

my %linenumbers = ();
while (<IN>)
chomp;
$linenumbers$_ = 1;


unless (open(IN, $ARGV[1]))
die "Can't open contents file '$ARGV[1]'n";

$. = 0;
while (<IN>)
print if defined $linenumbers$.;


exit;


This first reads the list of line numbers that we're interested in into an associative array, where the line numbers are the key. chomp removes the newline at the end of the line, $_ is the line itself.



Next the data file is opened, and when the line number is an existing key in the array of line numbers, then the line is printed.



The $. is perl's line number counter, this increments for every line read. As this is counted across files, I reset it to zero before reading any lines of the data file.



This could probably be written much more in "perl" style, but I prefer to keep it a bit more readable.



If the list of lines you want to extract is very large, this may not be the most efficient way, but I find that perl is often amazingly efficient at these things.



If you require the lines to be extracted in the order that they are listed, i.e. not sequentially, then it becomes a lot more complicated...






share|improve this answer






























    1














    Here are an alternative method and a bit of benchmarking, adding to that in Weijun Zhou's answer.



    join



    Assuming you have a data file you want to extract rows from and a line_numbers file that lists the numbers of the rows you want to extract, if the sorting order of the output is not important you can use:



    join <(sort padded_line_numbers) <(nl -w 12 -n rz data) | cut -d ' ' -f 2-


    This will number the lines of your data file, join it with the padded_line_numbers file on the first field (the default) and print out the common lines (excluding the join field itself, that is cut away).



    join needs the input files to be sorted alphabetically. The aforementioned padded_line_numbers file has to be prepared by left-padding each line of your line_numbers file. E.g.:



    while read rownum; do
    printf '%.12dn' "$rownum"
    done <line_numbers >padded_line_numbers


    The -w 12 -n rz options and arguments instruct nl to output 12 digits long numbers with leading zeros.



    If the sorting order of the output has to match that of your line_numbers file, you can use:



    join -1 2 -2 1 <(nl padded_line_numbers | sort -k 2,2) 
    <(nl -w 12 -n rz data) |
    sort -k 2,2n |
    cut -d ' ' -f 3-


    Where we are numbering the padded_line_numbers file, sorting the result alphabetically by its second field, joining it with the numbered data file and numerically sorting the result by the original sorting order of padded_line_numbers.



    Process substitution is here used for convenience. If you can not or do not want to rely on it and, as it is likely, you are not willing to waste the storage needed for creating regular files to hold intermediate results, you can leverage named pipes:



    mkfifo padded_line_numbers
    mkfifo numbered_data

    while read rownum; do
    printf '%.12dn' "$rownum"
    done <line_numbers | nl | sort -k 2,2 >padded_line_numbers &

    nl -w 12 -n rz data >numbered_data &

    join -1 2 -2 1 padded_line_numbers numbered_data | sort -k 2,2n | cut -d ' ' -f 3-


    Benchmarking



    Since the peculiarity of your question is the number of rows in your data file, I thought it could be useful to test alternative approaches with a comparable amount of data.



    For my tests I used a 3.2 billion lines data file. Each line is just 2 bytes of garbage coming from openssl enc, hex-encoded using od -An -tx1 -w2 and with spaces removed with tr -d ' ':



    $ head -n 3 data
    c15d
    061d
    5787

    $ wc -l data
    3221254963 data


    The line_numbers file has been created by randomly choosing 10,000 numbers between 1 and 3,221,254,963, without repetitions, using shuf from GNU Coreutils:



    shuf -i 1-"$(wc -l <data)" -n 10000 >line_numbers


    The testing environment was a laptop with a i7-2670QM Intel quad-core processor, 16 GiB of memory, SSD storage, GNU/Linux, bash 5.0 and GNU tools.

    The only dimension I measured has been the execution time, by means of the time shell builtin.



    Here I'm considering:



    • The sed solution from Weijun Zhou's answer.

    • The awk solution from Micha's answer.

    • The perl solution from wurtel's answer.

    • The join solution above.

    perl seems to be the fastest:



    $ time perl_script line_numbers data | wc -l
    10000

    real 14m51.597s
    user 14m41.878s
    sys 0m9.299s


    awk's performance looks comparable:



    $ time awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' line_numbers data | wc -l
    10000

    real 29m3.808s
    user 28m52.616s
    sys 0m10.709s


    join, too, appears to be comparable:



    $ time join <(sort padded_line_numbers) <(nl -w 12 -n rz data) | wc -l
    10000

    real 28m24.053s
    user 27m52.857s
    sys 0m28.958s


    Note that the sorted version mentioned above has roughly no performance penalty over this one.



    Finally, sed appears to be significantly slower: I killed it after approximately nine hours:



    $ time sed -nf <(sed 's/$/p/' line_numbers) data | wc -l
    ^C

    real 551m12.747s
    user 550m53.390s
    sys 0m15.624s





    share|improve this answer
































      0














      micha@linux-micha: /tmp
      $ cat numbers.txt
      1
      2
      4
      5

      micha@linux-micha: /tmp
      $ cat sentences.txt
      alpha
      bravo
      charlie
      delta
      echo
      foxtrott

      micha@linux-micha: /tmp
      $ awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' numbers.txt sentences.txt
      alpha
      bravo
      delta
      echo





      share|improve this answer

























      • This one invokes awk many times and will be really slow if sentences.txt is a huge file.

        – Weijun Zhou
        Mar 14 at 23:59











      • W. Zhou is right. Thank you! So I'll think twice.

        – Micha
        Mar 15 at 0:18






      • 1





        So, edited my 1st awk approach. Now awk is invoked 1x. May be this is fast enough?

        – Micha
        Mar 15 at 1:05










      Your Answer








      StackExchange.ready(function()
      var channelOptions =
      tags: "".split(" "),
      id: "106"
      ;
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function()
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled)
      StackExchange.using("snippets", function()
      createEditor();
      );

      else
      createEditor();

      );

      function createEditor()
      StackExchange.prepareEditor(
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader:
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      ,
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      );



      );













      draft saved

      draft discarded


















      StackExchange.ready(
      function ()
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506207%2ffast-way-to-extract-lines-from-a-large-file-with-80-billion-lines%23new-answer', 'question_page');

      );

      Post as a guest















      Required, but never shown

























      4 Answers
      4






      active

      oldest

      votes








      4 Answers
      4






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      2














      One liner, using sed:



      sed -nf <(sed 's/$/p/' linenumberfile) contentfile


      To keep the original order in linenumberfile, you can do



      sed -nf <(sed 's/$/p/' linenumberfile) contentfile | paste <(nl linenumberfile | sort -n -k 2,2) - | sort -n -k 1,1 | cut -f 3-


      Explanation:



      sed 's/$/p/' linenumberfile


      generates a sed script which prints the specified line. The script is then fed into another sed (with -n to suppress default printing of the pattern space) to do the actual printing. Since sed process the content file line by line, the output will be in the same order as in the content file. Note that this is a one-pass process so I would expect the speed to be acceptable.



      To accelerate the process, one can change p to p;b and add a q at the end of the generated sed script.



      To retain the order of the lines as they are in the line number file, nl is used to add "line numbers" to the line number file. So a line number file



      4
      5
      2


      would become



      1 4
      2 5
      3 2


      The first column records the original order in the line number file.



      The file with "line numbers" is then sorted and pasted to the output of sed, to make



      3 2 content_of_line2
      1 4 content_of_line4
      2 5 content_of_line5


      then it is sorted using the 1st column as the key, to finally obtain



      1 4 content_of_line4
      2 5 content_of_line5
      3 2 content_of_line2


      Finally, cut is used to remove the 2 extra columns.



      Benchmarking



      It seems sed would do best for a few lines, but perl is the way to go for 10000 lines as specified in the question.



      $ cat /proc/cpuinfo | grep -A 4 -m 1 processor
      processor : 0
      vendor_id : GenuineIntel
      cpu family : 6
      model : 60
      model name : Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz

      $ wc -l linenumber
      10 linenumber

      $ wc -l content
      8982457 content

      $ file content
      content: ASCII text

      $ time bash -c "sed -nf <(sed 's/$/p/' linenumber) content > /dev/null"
      real 0m0.791s
      user 0m0.661s
      sys 0m0.133s

      $ time bash -c "awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' linenumber content > /dev/null"
      real 0m3.061s
      user 0m2.908s
      sys 0m0.152s

      $ time bash -c "./ln.pl linenumber content > /dev/null"
      real 0m1.706s
      user 0m1.582s
      sys 0m0.124s

      $ ./genlinenumber.py 100 > linenumber
      $ wc -l linenumber
      100 linenumber

      $ time bash -c "sed -nf <(sed 's/$/p/' linenumber) content > /dev/null"
      real 0m3.326s
      user 0m3.164s
      sys 0m0.164s

      $ time bash -c "awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' linenumber content > /dev/null"
      real 0m3.055s
      user 0m2.890s
      sys 0m0.164s

      $ time bash -c "./ln.pl linenumber content > /dev/null"
      real 0m1.769s
      user 0m1.604s
      sys 0m0.165s


      If it is required to retain the order of lines, the command after the first | can still be used since the time is negligible.



      $ ./genlinenumber.py 10000 > linenumber
      $ wc -l linenumber
      10000 linenumber

      $ time bash -c "./ln.pl linenumber content > extract"
      real 0m1.933s
      user 0m1.791s
      sys 0m0.141s

      $ time bash -c "paste <(nl linenumber | sort -n -k 2,2) extract | sort -n -k 1,1 | cut -f 3- > /dev/null"
      real 0m0.018s
      user 0m0.012s
      sys 0m0.005s





      share|improve this answer




















      • 1





        Done. Suggestions are welcome.

        – Weijun Zhou
        Mar 14 at 8:58











      • Do common versions of sed support line numbers larger than 32 bits?

        – Nate Eldredge
        Mar 14 at 14:40






      • 1





        You are right. I made a mistake in last edits.

        – Weijun Zhou
        Mar 14 at 20:22











      • @NateEldredge I'm not sure about that.

        – Weijun Zhou
        Mar 15 at 0:01















      2














      One liner, using sed:



      sed -nf <(sed 's/$/p/' linenumberfile) contentfile


      To keep the original order in linenumberfile, you can do



      sed -nf <(sed 's/$/p/' linenumberfile) contentfile | paste <(nl linenumberfile | sort -n -k 2,2) - | sort -n -k 1,1 | cut -f 3-


      Explanation:



      sed 's/$/p/' linenumberfile


      generates a sed script which prints the specified line. The script is then fed into another sed (with -n to suppress default printing of the pattern space) to do the actual printing. Since sed process the content file line by line, the output will be in the same order as in the content file. Note that this is a one-pass process so I would expect the speed to be acceptable.



      To accelerate the process, one can change p to p;b and add a q at the end of the generated sed script.



      To retain the order of the lines as they are in the line number file, nl is used to add "line numbers" to the line number file. So a line number file



      4
      5
      2


      would become



      1 4
      2 5
      3 2


      The first column records the original order in the line number file.



      The file with "line numbers" is then sorted and pasted to the output of sed, to make



      3 2 content_of_line2
      1 4 content_of_line4
      2 5 content_of_line5


      then it is sorted using the 1st column as the key, to finally obtain



      1 4 content_of_line4
      2 5 content_of_line5
      3 2 content_of_line2


      Finally, cut is used to remove the 2 extra columns.



      Benchmarking



      It seems sed would do best for a few lines, but perl is the way to go for 10000 lines as specified in the question.



      $ cat /proc/cpuinfo | grep -A 4 -m 1 processor
      processor : 0
      vendor_id : GenuineIntel
      cpu family : 6
      model : 60
      model name : Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz

      $ wc -l linenumber
      10 linenumber

      $ wc -l content
      8982457 content

      $ file content
      content: ASCII text

      $ time bash -c "sed -nf <(sed 's/$/p/' linenumber) content > /dev/null"
      real 0m0.791s
      user 0m0.661s
      sys 0m0.133s

      $ time bash -c "awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' linenumber content > /dev/null"
      real 0m3.061s
      user 0m2.908s
      sys 0m0.152s

      $ time bash -c "./ln.pl linenumber content > /dev/null"
      real 0m1.706s
      user 0m1.582s
      sys 0m0.124s

      $ ./genlinenumber.py 100 > linenumber
      $ wc -l linenumber
      100 linenumber

      $ time bash -c "sed -nf <(sed 's/$/p/' linenumber) content > /dev/null"
      real 0m3.326s
      user 0m3.164s
      sys 0m0.164s

      $ time bash -c "awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' linenumber content > /dev/null"
      real 0m3.055s
      user 0m2.890s
      sys 0m0.164s

      $ time bash -c "./ln.pl linenumber content > /dev/null"
      real 0m1.769s
      user 0m1.604s
      sys 0m0.165s


      If it is required to retain the order of lines, the command after the first | can still be used since the time is negligible.



      $ ./genlinenumber.py 10000 > linenumber
      $ wc -l linenumber
      10000 linenumber

      $ time bash -c "./ln.pl linenumber content > extract"
      real 0m1.933s
      user 0m1.791s
      sys 0m0.141s

      $ time bash -c "paste <(nl linenumber | sort -n -k 2,2) extract | sort -n -k 1,1 | cut -f 3- > /dev/null"
      real 0m0.018s
      user 0m0.012s
      sys 0m0.005s





      share|improve this answer




















      • 1





        Done. Suggestions are welcome.

        – Weijun Zhou
        Mar 14 at 8:58











      • Do common versions of sed support line numbers larger than 32 bits?

        – Nate Eldredge
        Mar 14 at 14:40






      • 1





        You are right. I made a mistake in last edits.

        – Weijun Zhou
        Mar 14 at 20:22











      • @NateEldredge I'm not sure about that.

        – Weijun Zhou
        Mar 15 at 0:01













      2












      2








      2







      One liner, using sed:



      sed -nf <(sed 's/$/p/' linenumberfile) contentfile


      To keep the original order in linenumberfile, you can do



      sed -nf <(sed 's/$/p/' linenumberfile) contentfile | paste <(nl linenumberfile | sort -n -k 2,2) - | sort -n -k 1,1 | cut -f 3-


      Explanation:



      sed 's/$/p/' linenumberfile


      generates a sed script which prints the specified line. The script is then fed into another sed (with -n to suppress default printing of the pattern space) to do the actual printing. Since sed process the content file line by line, the output will be in the same order as in the content file. Note that this is a one-pass process so I would expect the speed to be acceptable.



      To accelerate the process, one can change p to p;b and add a q at the end of the generated sed script.



      To retain the order of the lines as they are in the line number file, nl is used to add "line numbers" to the line number file. So a line number file



      4
      5
      2


      would become



      1 4
      2 5
      3 2


      The first column records the original order in the line number file.



      The file with "line numbers" is then sorted and pasted to the output of sed, to make



      3 2 content_of_line2
      1 4 content_of_line4
      2 5 content_of_line5


      then it is sorted using the 1st column as the key, to finally obtain



      1 4 content_of_line4
      2 5 content_of_line5
      3 2 content_of_line2


      Finally, cut is used to remove the 2 extra columns.



      Benchmarking



      It seems sed would do best for a few lines, but perl is the way to go for 10000 lines as specified in the question.



      $ cat /proc/cpuinfo | grep -A 4 -m 1 processor
      processor : 0
      vendor_id : GenuineIntel
      cpu family : 6
      model : 60
      model name : Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz

      $ wc -l linenumber
      10 linenumber

      $ wc -l content
      8982457 content

      $ file content
      content: ASCII text

      $ time bash -c "sed -nf <(sed 's/$/p/' linenumber) content > /dev/null"
      real 0m0.791s
      user 0m0.661s
      sys 0m0.133s

      $ time bash -c "awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' linenumber content > /dev/null"
      real 0m3.061s
      user 0m2.908s
      sys 0m0.152s

      $ time bash -c "./ln.pl linenumber content > /dev/null"
      real 0m1.706s
      user 0m1.582s
      sys 0m0.124s

      $ ./genlinenumber.py 100 > linenumber
      $ wc -l linenumber
      100 linenumber

      $ time bash -c "sed -nf <(sed 's/$/p/' linenumber) content > /dev/null"
      real 0m3.326s
      user 0m3.164s
      sys 0m0.164s

      $ time bash -c "awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' linenumber content > /dev/null"
      real 0m3.055s
      user 0m2.890s
      sys 0m0.164s

      $ time bash -c "./ln.pl linenumber content > /dev/null"
      real 0m1.769s
      user 0m1.604s
      sys 0m0.165s


      If it is required to retain the order of lines, the command after the first | can still be used since the time is negligible.



      $ ./genlinenumber.py 10000 > linenumber
      $ wc -l linenumber
      10000 linenumber

      $ time bash -c "./ln.pl linenumber content > extract"
      real 0m1.933s
      user 0m1.791s
      sys 0m0.141s

      $ time bash -c "paste <(nl linenumber | sort -n -k 2,2) extract | sort -n -k 1,1 | cut -f 3- > /dev/null"
      real 0m0.018s
      user 0m0.012s
      sys 0m0.005s





      share|improve this answer















      One liner, using sed:



      sed -nf <(sed 's/$/p/' linenumberfile) contentfile


      To keep the original order in linenumberfile, you can do



      sed -nf <(sed 's/$/p/' linenumberfile) contentfile | paste <(nl linenumberfile | sort -n -k 2,2) - | sort -n -k 1,1 | cut -f 3-


      Explanation:



      sed 's/$/p/' linenumberfile


      generates a sed script which prints the specified line. The script is then fed into another sed (with -n to suppress default printing of the pattern space) to do the actual printing. Since sed process the content file line by line, the output will be in the same order as in the content file. Note that this is a one-pass process so I would expect the speed to be acceptable.



      To accelerate the process, one can change p to p;b and add a q at the end of the generated sed script.



      To retain the order of the lines as they are in the line number file, nl is used to add "line numbers" to the line number file. So a line number file



      4
      5
      2


      would become



      1 4
      2 5
      3 2


      The first column records the original order in the line number file.



      The file with "line numbers" is then sorted and pasted to the output of sed, to make



      3 2 content_of_line2
      1 4 content_of_line4
      2 5 content_of_line5


      then it is sorted using the 1st column as the key, to finally obtain



      1 4 content_of_line4
      2 5 content_of_line5
      3 2 content_of_line2


      Finally, cut is used to remove the 2 extra columns.



      Benchmarking



      It seems sed would do best for a few lines, but perl is the way to go for 10000 lines as specified in the question.



      $ cat /proc/cpuinfo | grep -A 4 -m 1 processor
      processor : 0
      vendor_id : GenuineIntel
      cpu family : 6
      model : 60
      model name : Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz

      $ wc -l linenumber
      10 linenumber

      $ wc -l content
      8982457 content

      $ file content
      content: ASCII text

      $ time bash -c "sed -nf <(sed 's/$/p/' linenumber) content > /dev/null"
      real 0m0.791s
      user 0m0.661s
      sys 0m0.133s

      $ time bash -c "awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' linenumber content > /dev/null"
      real 0m3.061s
      user 0m2.908s
      sys 0m0.152s

      $ time bash -c "./ln.pl linenumber content > /dev/null"
      real 0m1.706s
      user 0m1.582s
      sys 0m0.124s

      $ ./genlinenumber.py 100 > linenumber
      $ wc -l linenumber
      100 linenumber

      $ time bash -c "sed -nf <(sed 's/$/p/' linenumber) content > /dev/null"
      real 0m3.326s
      user 0m3.164s
      sys 0m0.164s

      $ time bash -c "awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' linenumber content > /dev/null"
      real 0m3.055s
      user 0m2.890s
      sys 0m0.164s

      $ time bash -c "./ln.pl linenumber content > /dev/null"
      real 0m1.769s
      user 0m1.604s
      sys 0m0.165s


      If it is required to retain the order of lines, the command after the first | can still be used since the time is negligible.



      $ ./genlinenumber.py 10000 > linenumber
      $ wc -l linenumber
      10000 linenumber

      $ time bash -c "./ln.pl linenumber content > extract"
      real 0m1.933s
      user 0m1.791s
      sys 0m0.141s

      $ time bash -c "paste <(nl linenumber | sort -n -k 2,2) extract | sort -n -k 1,1 | cut -f 3- > /dev/null"
      real 0m0.018s
      user 0m0.012s
      sys 0m0.005s






      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Mar 15 at 7:34

























      answered Mar 14 at 8:39









      Weijun ZhouWeijun Zhou

      1,575325




      1,575325







      • 1





        Done. Suggestions are welcome.

        – Weijun Zhou
        Mar 14 at 8:58











      • Do common versions of sed support line numbers larger than 32 bits?

        – Nate Eldredge
        Mar 14 at 14:40






      • 1





        You are right. I made a mistake in last edits.

        – Weijun Zhou
        Mar 14 at 20:22











      • @NateEldredge I'm not sure about that.

        – Weijun Zhou
        Mar 15 at 0:01












      • 1





        Done. Suggestions are welcome.

        – Weijun Zhou
        Mar 14 at 8:58











      • Do common versions of sed support line numbers larger than 32 bits?

        – Nate Eldredge
        Mar 14 at 14:40






      • 1





        You are right. I made a mistake in last edits.

        – Weijun Zhou
        Mar 14 at 20:22











      • @NateEldredge I'm not sure about that.

        – Weijun Zhou
        Mar 15 at 0:01







      1




      1





      Done. Suggestions are welcome.

      – Weijun Zhou
      Mar 14 at 8:58





      Done. Suggestions are welcome.

      – Weijun Zhou
      Mar 14 at 8:58













      Do common versions of sed support line numbers larger than 32 bits?

      – Nate Eldredge
      Mar 14 at 14:40





      Do common versions of sed support line numbers larger than 32 bits?

      – Nate Eldredge
      Mar 14 at 14:40




      1




      1





      You are right. I made a mistake in last edits.

      – Weijun Zhou
      Mar 14 at 20:22





      You are right. I made a mistake in last edits.

      – Weijun Zhou
      Mar 14 at 20:22













      @NateEldredge I'm not sure about that.

      – Weijun Zhou
      Mar 15 at 0:01





      @NateEldredge I'm not sure about that.

      – Weijun Zhou
      Mar 15 at 0:01













      1














      I would use a perl script for this. I came up with this:



      #!/usr/bin/perl

      # usage: thisscript linenumberslist.txt contentsfile

      unless (open(IN, $ARGV[0]))
      die "Can't open list of line numbers file '$ARGV[0]'n";

      my %linenumbers = ();
      while (<IN>)
      chomp;
      $linenumbers$_ = 1;


      unless (open(IN, $ARGV[1]))
      die "Can't open contents file '$ARGV[1]'n";

      $. = 0;
      while (<IN>)
      print if defined $linenumbers$.;


      exit;


      This first reads the list of line numbers that we're interested in into an associative array, where the line numbers are the key. chomp removes the newline at the end of the line, $_ is the line itself.



      Next the data file is opened, and when the line number is an existing key in the array of line numbers, then the line is printed.



      The $. is perl's line number counter, this increments for every line read. As this is counted across files, I reset it to zero before reading any lines of the data file.



      This could probably be written much more in "perl" style, but I prefer to keep it a bit more readable.



      If the list of lines you want to extract is very large, this may not be the most efficient way, but I find that perl is often amazingly efficient at these things.



      If you require the lines to be extracted in the order that they are listed, i.e. not sequentially, then it becomes a lot more complicated...






      share|improve this answer



























        1














        I would use a perl script for this. I came up with this:



        #!/usr/bin/perl

        # usage: thisscript linenumberslist.txt contentsfile

        unless (open(IN, $ARGV[0]))
        die "Can't open list of line numbers file '$ARGV[0]'n";

        my %linenumbers = ();
        while (<IN>)
        chomp;
        $linenumbers$_ = 1;


        unless (open(IN, $ARGV[1]))
        die "Can't open contents file '$ARGV[1]'n";

        $. = 0;
        while (<IN>)
        print if defined $linenumbers$.;


        exit;


        This first reads the list of line numbers that we're interested in into an associative array, where the line numbers are the key. chomp removes the newline at the end of the line, $_ is the line itself.



        Next the data file is opened, and when the line number is an existing key in the array of line numbers, then the line is printed.



        The $. is perl's line number counter, this increments for every line read. As this is counted across files, I reset it to zero before reading any lines of the data file.



        This could probably be written much more in "perl" style, but I prefer to keep it a bit more readable.



        If the list of lines you want to extract is very large, this may not be the most efficient way, but I find that perl is often amazingly efficient at these things.



        If you require the lines to be extracted in the order that they are listed, i.e. not sequentially, then it becomes a lot more complicated...






        share|improve this answer

























          1












          1








          1







          I would use a perl script for this. I came up with this:



          #!/usr/bin/perl

          # usage: thisscript linenumberslist.txt contentsfile

          unless (open(IN, $ARGV[0]))
          die "Can't open list of line numbers file '$ARGV[0]'n";

          my %linenumbers = ();
          while (<IN>)
          chomp;
          $linenumbers$_ = 1;


          unless (open(IN, $ARGV[1]))
          die "Can't open contents file '$ARGV[1]'n";

          $. = 0;
          while (<IN>)
          print if defined $linenumbers$.;


          exit;


          This first reads the list of line numbers that we're interested in into an associative array, where the line numbers are the key. chomp removes the newline at the end of the line, $_ is the line itself.



          Next the data file is opened, and when the line number is an existing key in the array of line numbers, then the line is printed.



          The $. is perl's line number counter, this increments for every line read. As this is counted across files, I reset it to zero before reading any lines of the data file.



          This could probably be written much more in "perl" style, but I prefer to keep it a bit more readable.



          If the list of lines you want to extract is very large, this may not be the most efficient way, but I find that perl is often amazingly efficient at these things.



          If you require the lines to be extracted in the order that they are listed, i.e. not sequentially, then it becomes a lot more complicated...






          share|improve this answer













          I would use a perl script for this. I came up with this:



          #!/usr/bin/perl

          # usage: thisscript linenumberslist.txt contentsfile

          unless (open(IN, $ARGV[0]))
          die "Can't open list of line numbers file '$ARGV[0]'n";

          my %linenumbers = ();
          while (<IN>)
          chomp;
          $linenumbers$_ = 1;


          unless (open(IN, $ARGV[1]))
          die "Can't open contents file '$ARGV[1]'n";

          $. = 0;
          while (<IN>)
          print if defined $linenumbers$.;


          exit;


          This first reads the list of line numbers that we're interested in into an associative array, where the line numbers are the key. chomp removes the newline at the end of the line, $_ is the line itself.



          Next the data file is opened, and when the line number is an existing key in the array of line numbers, then the line is printed.



          The $. is perl's line number counter, this increments for every line read. As this is counted across files, I reset it to zero before reading any lines of the data file.



          This could probably be written much more in "perl" style, but I prefer to keep it a bit more readable.



          If the list of lines you want to extract is very large, this may not be the most efficient way, but I find that perl is often amazingly efficient at these things.



          If you require the lines to be extracted in the order that they are listed, i.e. not sequentially, then it becomes a lot more complicated...







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Mar 14 at 7:26









          wurtelwurtel

          11k11628




          11k11628





















              1














              Here are an alternative method and a bit of benchmarking, adding to that in Weijun Zhou's answer.



              join



              Assuming you have a data file you want to extract rows from and a line_numbers file that lists the numbers of the rows you want to extract, if the sorting order of the output is not important you can use:



              join <(sort padded_line_numbers) <(nl -w 12 -n rz data) | cut -d ' ' -f 2-


              This will number the lines of your data file, join it with the padded_line_numbers file on the first field (the default) and print out the common lines (excluding the join field itself, that is cut away).



              join needs the input files to be sorted alphabetically. The aforementioned padded_line_numbers file has to be prepared by left-padding each line of your line_numbers file. E.g.:



              while read rownum; do
              printf '%.12dn' "$rownum"
              done <line_numbers >padded_line_numbers


              The -w 12 -n rz options and arguments instruct nl to output 12 digits long numbers with leading zeros.



              If the sorting order of the output has to match that of your line_numbers file, you can use:



              join -1 2 -2 1 <(nl padded_line_numbers | sort -k 2,2) 
              <(nl -w 12 -n rz data) |
              sort -k 2,2n |
              cut -d ' ' -f 3-


              Where we are numbering the padded_line_numbers file, sorting the result alphabetically by its second field, joining it with the numbered data file and numerically sorting the result by the original sorting order of padded_line_numbers.



              Process substitution is here used for convenience. If you can not or do not want to rely on it and, as it is likely, you are not willing to waste the storage needed for creating regular files to hold intermediate results, you can leverage named pipes:



              mkfifo padded_line_numbers
              mkfifo numbered_data

              while read rownum; do
              printf '%.12dn' "$rownum"
              done <line_numbers | nl | sort -k 2,2 >padded_line_numbers &

              nl -w 12 -n rz data >numbered_data &

              join -1 2 -2 1 padded_line_numbers numbered_data | sort -k 2,2n | cut -d ' ' -f 3-


              Benchmarking



              Since the peculiarity of your question is the number of rows in your data file, I thought it could be useful to test alternative approaches with a comparable amount of data.



              For my tests I used a 3.2 billion lines data file. Each line is just 2 bytes of garbage coming from openssl enc, hex-encoded using od -An -tx1 -w2 and with spaces removed with tr -d ' ':



              $ head -n 3 data
              c15d
              061d
              5787

              $ wc -l data
              3221254963 data


              The line_numbers file has been created by randomly choosing 10,000 numbers between 1 and 3,221,254,963, without repetitions, using shuf from GNU Coreutils:



              shuf -i 1-"$(wc -l <data)" -n 10000 >line_numbers


              The testing environment was a laptop with a i7-2670QM Intel quad-core processor, 16 GiB of memory, SSD storage, GNU/Linux, bash 5.0 and GNU tools.

              The only dimension I measured has been the execution time, by means of the time shell builtin.



              Here I'm considering:



              • The sed solution from Weijun Zhou's answer.

              • The awk solution from Micha's answer.

              • The perl solution from wurtel's answer.

              • The join solution above.

              perl seems to be the fastest:



              $ time perl_script line_numbers data | wc -l
              10000

              real 14m51.597s
              user 14m41.878s
              sys 0m9.299s


              awk's performance looks comparable:



              $ time awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' line_numbers data | wc -l
              10000

              real 29m3.808s
              user 28m52.616s
              sys 0m10.709s


              join, too, appears to be comparable:



              $ time join <(sort padded_line_numbers) <(nl -w 12 -n rz data) | wc -l
              10000

              real 28m24.053s
              user 27m52.857s
              sys 0m28.958s


              Note that the sorted version mentioned above has roughly no performance penalty over this one.



              Finally, sed appears to be significantly slower: I killed it after approximately nine hours:



              $ time sed -nf <(sed 's/$/p/' line_numbers) data | wc -l
              ^C

              real 551m12.747s
              user 550m53.390s
              sys 0m15.624s





              share|improve this answer





























                1














                Here are an alternative method and a bit of benchmarking, adding to that in Weijun Zhou's answer.



                join



                Assuming you have a data file you want to extract rows from and a line_numbers file that lists the numbers of the rows you want to extract, if the sorting order of the output is not important you can use:



                join <(sort padded_line_numbers) <(nl -w 12 -n rz data) | cut -d ' ' -f 2-


                This will number the lines of your data file, join it with the padded_line_numbers file on the first field (the default) and print out the common lines (excluding the join field itself, that is cut away).



                join needs the input files to be sorted alphabetically. The aforementioned padded_line_numbers file has to be prepared by left-padding each line of your line_numbers file. E.g.:



                while read rownum; do
                printf '%.12dn' "$rownum"
                done <line_numbers >padded_line_numbers


                The -w 12 -n rz options and arguments instruct nl to output 12 digits long numbers with leading zeros.



                If the sorting order of the output has to match that of your line_numbers file, you can use:



                join -1 2 -2 1 <(nl padded_line_numbers | sort -k 2,2) 
                <(nl -w 12 -n rz data) |
                sort -k 2,2n |
                cut -d ' ' -f 3-


                Where we are numbering the padded_line_numbers file, sorting the result alphabetically by its second field, joining it with the numbered data file and numerically sorting the result by the original sorting order of padded_line_numbers.



                Process substitution is here used for convenience. If you can not or do not want to rely on it and, as it is likely, you are not willing to waste the storage needed for creating regular files to hold intermediate results, you can leverage named pipes:



                mkfifo padded_line_numbers
                mkfifo numbered_data

                while read rownum; do
                printf '%.12dn' "$rownum"
                done <line_numbers | nl | sort -k 2,2 >padded_line_numbers &

                nl -w 12 -n rz data >numbered_data &

                join -1 2 -2 1 padded_line_numbers numbered_data | sort -k 2,2n | cut -d ' ' -f 3-


                Benchmarking



                Since the peculiarity of your question is the number of rows in your data file, I thought it could be useful to test alternative approaches with a comparable amount of data.



                For my tests I used a 3.2 billion lines data file. Each line is just 2 bytes of garbage coming from openssl enc, hex-encoded using od -An -tx1 -w2 and with spaces removed with tr -d ' ':



                $ head -n 3 data
                c15d
                061d
                5787

                $ wc -l data
                3221254963 data


                The line_numbers file has been created by randomly choosing 10,000 numbers between 1 and 3,221,254,963, without repetitions, using shuf from GNU Coreutils:



                shuf -i 1-"$(wc -l <data)" -n 10000 >line_numbers


                The testing environment was a laptop with a i7-2670QM Intel quad-core processor, 16 GiB of memory, SSD storage, GNU/Linux, bash 5.0 and GNU tools.

                The only dimension I measured has been the execution time, by means of the time shell builtin.



                Here I'm considering:



                • The sed solution from Weijun Zhou's answer.

                • The awk solution from Micha's answer.

                • The perl solution from wurtel's answer.

                • The join solution above.

                perl seems to be the fastest:



                $ time perl_script line_numbers data | wc -l
                10000

                real 14m51.597s
                user 14m41.878s
                sys 0m9.299s


                awk's performance looks comparable:



                $ time awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' line_numbers data | wc -l
                10000

                real 29m3.808s
                user 28m52.616s
                sys 0m10.709s


                join, too, appears to be comparable:



                $ time join <(sort padded_line_numbers) <(nl -w 12 -n rz data) | wc -l
                10000

                real 28m24.053s
                user 27m52.857s
                sys 0m28.958s


                Note that the sorted version mentioned above has roughly no performance penalty over this one.



                Finally, sed appears to be significantly slower: I killed it after approximately nine hours:



                $ time sed -nf <(sed 's/$/p/' line_numbers) data | wc -l
                ^C

                real 551m12.747s
                user 550m53.390s
                sys 0m15.624s





                share|improve this answer



























                  1












                  1








                  1







                  Here are an alternative method and a bit of benchmarking, adding to that in Weijun Zhou's answer.



                  join



                  Assuming you have a data file you want to extract rows from and a line_numbers file that lists the numbers of the rows you want to extract, if the sorting order of the output is not important you can use:



                  join <(sort padded_line_numbers) <(nl -w 12 -n rz data) | cut -d ' ' -f 2-


                  This will number the lines of your data file, join it with the padded_line_numbers file on the first field (the default) and print out the common lines (excluding the join field itself, that is cut away).



                  join needs the input files to be sorted alphabetically. The aforementioned padded_line_numbers file has to be prepared by left-padding each line of your line_numbers file. E.g.:



                  while read rownum; do
                  printf '%.12dn' "$rownum"
                  done <line_numbers >padded_line_numbers


                  The -w 12 -n rz options and arguments instruct nl to output 12 digits long numbers with leading zeros.



                  If the sorting order of the output has to match that of your line_numbers file, you can use:



                  join -1 2 -2 1 <(nl padded_line_numbers | sort -k 2,2) 
                  <(nl -w 12 -n rz data) |
                  sort -k 2,2n |
                  cut -d ' ' -f 3-


                  Where we are numbering the padded_line_numbers file, sorting the result alphabetically by its second field, joining it with the numbered data file and numerically sorting the result by the original sorting order of padded_line_numbers.



                  Process substitution is here used for convenience. If you can not or do not want to rely on it and, as it is likely, you are not willing to waste the storage needed for creating regular files to hold intermediate results, you can leverage named pipes:



                  mkfifo padded_line_numbers
                  mkfifo numbered_data

                  while read rownum; do
                  printf '%.12dn' "$rownum"
                  done <line_numbers | nl | sort -k 2,2 >padded_line_numbers &

                  nl -w 12 -n rz data >numbered_data &

                  join -1 2 -2 1 padded_line_numbers numbered_data | sort -k 2,2n | cut -d ' ' -f 3-


                  Benchmarking



                  Since the peculiarity of your question is the number of rows in your data file, I thought it could be useful to test alternative approaches with a comparable amount of data.



                  For my tests I used a 3.2 billion lines data file. Each line is just 2 bytes of garbage coming from openssl enc, hex-encoded using od -An -tx1 -w2 and with spaces removed with tr -d ' ':



                  $ head -n 3 data
                  c15d
                  061d
                  5787

                  $ wc -l data
                  3221254963 data


                  The line_numbers file has been created by randomly choosing 10,000 numbers between 1 and 3,221,254,963, without repetitions, using shuf from GNU Coreutils:



                  shuf -i 1-"$(wc -l <data)" -n 10000 >line_numbers


                  The testing environment was a laptop with a i7-2670QM Intel quad-core processor, 16 GiB of memory, SSD storage, GNU/Linux, bash 5.0 and GNU tools.

                  The only dimension I measured has been the execution time, by means of the time shell builtin.



                  Here I'm considering:



                  • The sed solution from Weijun Zhou's answer.

                  • The awk solution from Micha's answer.

                  • The perl solution from wurtel's answer.

                  • The join solution above.

                  perl seems to be the fastest:



                  $ time perl_script line_numbers data | wc -l
                  10000

                  real 14m51.597s
                  user 14m41.878s
                  sys 0m9.299s


                  awk's performance looks comparable:



                  $ time awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' line_numbers data | wc -l
                  10000

                  real 29m3.808s
                  user 28m52.616s
                  sys 0m10.709s


                  join, too, appears to be comparable:



                  $ time join <(sort padded_line_numbers) <(nl -w 12 -n rz data) | wc -l
                  10000

                  real 28m24.053s
                  user 27m52.857s
                  sys 0m28.958s


                  Note that the sorted version mentioned above has roughly no performance penalty over this one.



                  Finally, sed appears to be significantly slower: I killed it after approximately nine hours:



                  $ time sed -nf <(sed 's/$/p/' line_numbers) data | wc -l
                  ^C

                  real 551m12.747s
                  user 550m53.390s
                  sys 0m15.624s





                  share|improve this answer















                  Here are an alternative method and a bit of benchmarking, adding to that in Weijun Zhou's answer.



                  join



                  Assuming you have a data file you want to extract rows from and a line_numbers file that lists the numbers of the rows you want to extract, if the sorting order of the output is not important you can use:



                  join <(sort padded_line_numbers) <(nl -w 12 -n rz data) | cut -d ' ' -f 2-


                  This will number the lines of your data file, join it with the padded_line_numbers file on the first field (the default) and print out the common lines (excluding the join field itself, that is cut away).



                  join needs the input files to be sorted alphabetically. The aforementioned padded_line_numbers file has to be prepared by left-padding each line of your line_numbers file. E.g.:



                  while read rownum; do
                  printf '%.12dn' "$rownum"
                  done <line_numbers >padded_line_numbers


                  The -w 12 -n rz options and arguments instruct nl to output 12 digits long numbers with leading zeros.



                  If the sorting order of the output has to match that of your line_numbers file, you can use:



                  join -1 2 -2 1 <(nl padded_line_numbers | sort -k 2,2) 
                  <(nl -w 12 -n rz data) |
                  sort -k 2,2n |
                  cut -d ' ' -f 3-


                  Where we are numbering the padded_line_numbers file, sorting the result alphabetically by its second field, joining it with the numbered data file and numerically sorting the result by the original sorting order of padded_line_numbers.



                  Process substitution is here used for convenience. If you can not or do not want to rely on it and, as it is likely, you are not willing to waste the storage needed for creating regular files to hold intermediate results, you can leverage named pipes:



                  mkfifo padded_line_numbers
                  mkfifo numbered_data

                  while read rownum; do
                  printf '%.12dn' "$rownum"
                  done <line_numbers | nl | sort -k 2,2 >padded_line_numbers &

                  nl -w 12 -n rz data >numbered_data &

                  join -1 2 -2 1 padded_line_numbers numbered_data | sort -k 2,2n | cut -d ' ' -f 3-


                  Benchmarking



                  Since the peculiarity of your question is the number of rows in your data file, I thought it could be useful to test alternative approaches with a comparable amount of data.



                  For my tests I used a 3.2 billion lines data file. Each line is just 2 bytes of garbage coming from openssl enc, hex-encoded using od -An -tx1 -w2 and with spaces removed with tr -d ' ':



                  $ head -n 3 data
                  c15d
                  061d
                  5787

                  $ wc -l data
                  3221254963 data


                  The line_numbers file has been created by randomly choosing 10,000 numbers between 1 and 3,221,254,963, without repetitions, using shuf from GNU Coreutils:



                  shuf -i 1-"$(wc -l <data)" -n 10000 >line_numbers


                  The testing environment was a laptop with a i7-2670QM Intel quad-core processor, 16 GiB of memory, SSD storage, GNU/Linux, bash 5.0 and GNU tools.

                  The only dimension I measured has been the execution time, by means of the time shell builtin.



                  Here I'm considering:



                  • The sed solution from Weijun Zhou's answer.

                  • The awk solution from Micha's answer.

                  • The perl solution from wurtel's answer.

                  • The join solution above.

                  perl seems to be the fastest:



                  $ time perl_script line_numbers data | wc -l
                  10000

                  real 14m51.597s
                  user 14m41.878s
                  sys 0m9.299s


                  awk's performance looks comparable:



                  $ time awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' line_numbers data | wc -l
                  10000

                  real 29m3.808s
                  user 28m52.616s
                  sys 0m10.709s


                  join, too, appears to be comparable:



                  $ time join <(sort padded_line_numbers) <(nl -w 12 -n rz data) | wc -l
                  10000

                  real 28m24.053s
                  user 27m52.857s
                  sys 0m28.958s


                  Note that the sorted version mentioned above has roughly no performance penalty over this one.



                  Finally, sed appears to be significantly slower: I killed it after approximately nine hours:



                  $ time sed -nf <(sed 's/$/p/' line_numbers) data | wc -l
                  ^C

                  real 551m12.747s
                  user 550m53.390s
                  sys 0m15.624s






                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited 1 hour ago

























                  answered 10 hours ago









                  fra-sanfra-san

                  1,8611520




                  1,8611520





















                      0














                      micha@linux-micha: /tmp
                      $ cat numbers.txt
                      1
                      2
                      4
                      5

                      micha@linux-micha: /tmp
                      $ cat sentences.txt
                      alpha
                      bravo
                      charlie
                      delta
                      echo
                      foxtrott

                      micha@linux-micha: /tmp
                      $ awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' numbers.txt sentences.txt
                      alpha
                      bravo
                      delta
                      echo





                      share|improve this answer

























                      • This one invokes awk many times and will be really slow if sentences.txt is a huge file.

                        – Weijun Zhou
                        Mar 14 at 23:59











                      • W. Zhou is right. Thank you! So I'll think twice.

                        – Micha
                        Mar 15 at 0:18






                      • 1





                        So, edited my 1st awk approach. Now awk is invoked 1x. May be this is fast enough?

                        – Micha
                        Mar 15 at 1:05















                      0














                      micha@linux-micha: /tmp
                      $ cat numbers.txt
                      1
                      2
                      4
                      5

                      micha@linux-micha: /tmp
                      $ cat sentences.txt
                      alpha
                      bravo
                      charlie
                      delta
                      echo
                      foxtrott

                      micha@linux-micha: /tmp
                      $ awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' numbers.txt sentences.txt
                      alpha
                      bravo
                      delta
                      echo





                      share|improve this answer

























                      • This one invokes awk many times and will be really slow if sentences.txt is a huge file.

                        – Weijun Zhou
                        Mar 14 at 23:59











                      • W. Zhou is right. Thank you! So I'll think twice.

                        – Micha
                        Mar 15 at 0:18






                      • 1





                        So, edited my 1st awk approach. Now awk is invoked 1x. May be this is fast enough?

                        – Micha
                        Mar 15 at 1:05













                      0












                      0








                      0







                      micha@linux-micha: /tmp
                      $ cat numbers.txt
                      1
                      2
                      4
                      5

                      micha@linux-micha: /tmp
                      $ cat sentences.txt
                      alpha
                      bravo
                      charlie
                      delta
                      echo
                      foxtrott

                      micha@linux-micha: /tmp
                      $ awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' numbers.txt sentences.txt
                      alpha
                      bravo
                      delta
                      echo





                      share|improve this answer















                      micha@linux-micha: /tmp
                      $ cat numbers.txt
                      1
                      2
                      4
                      5

                      micha@linux-micha: /tmp
                      $ cat sentences.txt
                      alpha
                      bravo
                      charlie
                      delta
                      echo
                      foxtrott

                      micha@linux-micha: /tmp
                      $ awk 'FNR==NR seen[$0]++ ; FNR!=NR && FNR in seen' numbers.txt sentences.txt
                      alpha
                      bravo
                      delta
                      echo






                      share|improve this answer














                      share|improve this answer



                      share|improve this answer








                      edited Mar 15 at 1:03

























                      answered Mar 14 at 23:55









                      MichaMicha

                      973




                      973












                      • This one invokes awk many times and will be really slow if sentences.txt is a huge file.

                        – Weijun Zhou
                        Mar 14 at 23:59











                      • W. Zhou is right. Thank you! So I'll think twice.

                        – Micha
                        Mar 15 at 0:18






                      • 1





                        So, edited my 1st awk approach. Now awk is invoked 1x. May be this is fast enough?

                        – Micha
                        Mar 15 at 1:05

















                      • This one invokes awk many times and will be really slow if sentences.txt is a huge file.

                        – Weijun Zhou
                        Mar 14 at 23:59











                      • W. Zhou is right. Thank you! So I'll think twice.

                        – Micha
                        Mar 15 at 0:18






                      • 1





                        So, edited my 1st awk approach. Now awk is invoked 1x. May be this is fast enough?

                        – Micha
                        Mar 15 at 1:05
















                      This one invokes awk many times and will be really slow if sentences.txt is a huge file.

                      – Weijun Zhou
                      Mar 14 at 23:59





                      This one invokes awk many times and will be really slow if sentences.txt is a huge file.

                      – Weijun Zhou
                      Mar 14 at 23:59













                      W. Zhou is right. Thank you! So I'll think twice.

                      – Micha
                      Mar 15 at 0:18





                      W. Zhou is right. Thank you! So I'll think twice.

                      – Micha
                      Mar 15 at 0:18




                      1




                      1





                      So, edited my 1st awk approach. Now awk is invoked 1x. May be this is fast enough?

                      – Micha
                      Mar 15 at 1:05





                      So, edited my 1st awk approach. Now awk is invoked 1x. May be this is fast enough?

                      – Micha
                      Mar 15 at 1:05

















                      draft saved

                      draft discarded
















































                      Thanks for contributing an answer to Unix & Linux Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid


                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.

                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function ()
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506207%2ffast-way-to-extract-lines-from-a-large-file-with-80-billion-lines%23new-answer', 'question_page');

                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Àrd-bhaile Cathair chruinne/Baile mòr cruinne | Artagailean ceangailte | Clàr-taice na seòladaireachd

                      대한민국 목차 국명 지리 역사 정치 국방 경제 사회 문화 국제 순위 관련 항목 각주 외부 링크 둘러보기 메뉴북위 37° 34′ 08″ 동경 126° 58′ 36″ / 북위 37.568889° 동경 126.976667°  / 37.568889; 126.976667ehThe Korean Repository문단을 편집문단을 편집추가해Clarkson PLC 사Report for Selected Countries and Subjects-Korea“Human Development Index and its components: P.198”“http://www.law.go.kr/%EB%B2%95%EB%A0%B9/%EB%8C%80%ED%95%9C%EB%AF%BC%EA%B5%AD%EA%B5%AD%EA%B8%B0%EB%B2%95”"한국은 국제법상 한반도 유일 합법정부 아니다" - 오마이뉴스 모바일Report for Selected Countries and Subjects: South Korea격동의 역사와 함께한 조선일보 90년 : 조선일보 인수해 혁신시킨 신석우, 임시정부 때는 '대한민국' 국호(國號) 정해《우리가 몰랐던 우리 역사: 나라 이름의 비밀을 찾아가는 역사 여행》“남북 공식호칭 ‘남한’‘북한’으로 쓴다”“Corea 대 Korea, 누가 이긴 거야?”국내기후자료 - 한국[김대중 前 대통령 서거] 과감한 구조개혁 'DJ노믹스'로 최단기간 환란극복 :: 네이버 뉴스“이라크 "韓-쿠르드 유전개발 MOU 승인 안해"(종합)”“해외 우리국민 추방사례 43%가 일본”차기전차 K2'흑표'의 세계 최고 전력 분석, 쿠키뉴스 엄기영, 2007-03-02두산인프라, 헬기잡는 장갑차 'K21'...내년부터 공급, 고뉴스 이대준, 2008-10-30과거 내용 찾기mk 뉴스 - 구매력 기준으로 보면 한국 1인당 소득 3만弗과거 내용 찾기"The N-11: More Than an Acronym"Archived조선일보 최우석, 2008-11-01Global 500 2008: Countries - South Korea“몇년째 '시한폭탄'... 가계부채, 올해는 터질까”가구당 부채 5000만원 처음 넘어서“‘빚’으로 내몰리는 사회.. 위기의 가계대출”“[경제365] 공공부문 부채 급증…800조 육박”“"소득 양극화 다소 완화...불평등은 여전"”“공정사회·공생발전 한참 멀었네”iSuppli,08年2QのDRAMシェア・ランキングを発表(08/8/11)South Korea dominates shipbuilding industry | Stock Market News & Stocks to Watch from StraightStocks한국 자동차 생산, 3년 연속 세계 5위자동차수출 '현대-삼성 웃고 기아-대우-쌍용은 울고' 과거 내용 찾기동반성장위 창립 1주년 맞아Archived"중기적합 3개업종 합의 무시한 채 선정"李대통령, 사업 무분별 확장 소상공인 생계 위협 질타삼성-LG, 서민업종인 빵·분식사업 잇따라 철수상생은 뒷전…SSM ‘몸집 불리기’ 혈안Archived“경부고속도에 '아시안하이웨이' 표지판”'철의 실크로드' 앞서 '말(言)의 실크로드'부터, 프레시안 정창현, 2008-10-01“'서울 지하철은 안전한가?'”“서울시 “올해 안에 모든 지하철역 스크린도어 설치””“부산지하철 1,2호선 승강장 안전펜스 설치 완료”“전교조, 정부 노조 통계서 처음 빠져”“[Weekly BIZ] 도요타 '제로 이사회'가 리콜 사태 불러들였다”“S Korea slams high tuition costs”““정치가 여론 양극화 부채질… 합리주의 절실””“〈"`촛불집회'는 민주주의의 질적 변화 상징"〉”““촛불집회가 민주주의 왜곡 초래””“국민 65%, "한국 노사관계 대립적"”“한국 국가경쟁력 27위‥노사관계 '꼴찌'”“제대로 형성되지 않은 대한민국 이념지형”“[신년기획-갈등의 시대] 갈등지수 OECD 4위…사회적 손실 GDP 27% 무려 300조”“2012 총선-대선의 키워드는 '국민과 소통'”“한국 삶의 질 27위, 2000년과 2008년 연속 하위권 머물러”“[해피 코리아] 행복점수 68점…해외 평가선 '낙제점'”“한국 어린이·청소년 행복지수 3년 연속 OECD ‘꼴찌’”“한국 이혼율 OECD중 8위”“[통계청] 한국 이혼율 OECD 4위”“오피니언 [이렇게 생각한다] `부부의 날` 에 돌아본 이혼율 1위 한국”“Suicide Rates by Country, Global Health Observatory Data Repository.”“1. 또 다른 차별”“오피니언 [편집자에게] '왕따'와 '패거리 정치' 심리는 닮은꼴”“[미래한국리포트] 무한경쟁에 빠진 대한민국”“대학생 98% "외모가 경쟁력이라는 말 동의"”“특급호텔 웨딩·200만원대 유모차… "남보다 더…" 호화病, 고질병 됐다”“[스트레스 공화국] ① 경쟁사회, 스트레스 쌓인다”““매일 30여명 자살 한국, 의사보다 무속인에…””“"자살 부르는 '우울증', 환자 중 85% 치료 안 받아"”“정신병원을 가다”“대한민국도 ‘묻지마 범죄’,안전지대 아니다”“유엔 "학생 '성적 지향'에 따른 차별 금지하라"”“유엔아동권리위원회 보고서 및 번역본 원문”“고졸 성공스토리 담은 '제빵왕 김탁구' 드라마 나온다”“‘빛 좋은 개살구’ 고졸 취업…실습 대신 착취”원본 문서“정신건강, 사회적 편견부터 고쳐드립니다”‘소통’과 ‘행복’에 목 마른 사회가 잠들어 있던 ‘심리학’ 깨웠다“[포토] 사유리-곽금주 교수의 유쾌한 심리상담”“"올해 한국인 평균 영화관람횟수 세계 1위"(종합)”“[게임연중기획] 게임은 문화다-여가활동 1순위 게임”“영화속 ‘영어 지상주의’ …“왠지 씁쓸한데””“2월 `신문 부수 인증기관` 지정..방송법 후속작업”“무료신문 성장동력 ‘차별성’과 ‘갈등해소’”대한민국 국회 법률지식정보시스템"Pew Research Center's Religion & Public Life Project: South Korea"“amp;vwcd=MT_ZTITLE&path=인구·가구%20>%20인구총조사%20>%20인구부문%20>%20 총조사인구(2005)%20>%20전수부문&oper_YN=Y&item=&keyword=종교별%20인구& amp;lang_mode=kor&list_id= 2005년 통계청 인구 총조사”원본 문서“한국인이 좋아하는 취미와 운동 (2004-2009)”“한국인이 좋아하는 취미와 운동 (2004-2014)”Archived“한국, `부분적 언론자유국' 강등〈프리덤하우스〉”“국경없는기자회 "한국, 인터넷감시 대상국"”“한국, 조선산업 1위 유지(S. Korea Stays Top Shipbuilding Nation) RZD-Partner Portal”원본 문서“한국, 4년 만에 ‘선박건조 1위’”“옛 마산시,인터넷속도 세계 1위”“"한국 초고속 인터넷망 세계1위"”“인터넷·휴대폰 요금, 외국보다 훨씬 비싸”“한국 관세행정 6년 연속 세계 '1위'”“한국 교통사고 사망자 수 OECD 회원국 중 2위”“결핵 후진국' 한국, 환자가 급증한 이유는”“수술은 신중해야… 자칫하면 생명 위협”대한민국분류대한민국의 지도대한민국 정부대표 다국어포털대한민국 전자정부대한민국 국회한국방송공사about korea and information korea브리태니커 백과사전(한국편)론리플래닛의 정보(한국편)CIA의 세계 정보(한국편)마리암 부디아 (Mariam Budia),『한국: 하늘이 내린 한 폭의 그림』, 서울: 트랜스라틴 19호 (2012년 3월)대한민국ehehehehehehehehehehehehehehWorldCat132441370n791268020000 0001 2308 81034078029-6026373548cb11863345f(데이터)00573706ge128495

                      Cannot Extend partition with GParted The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) 2019 Community Moderator Election ResultsCan't increase partition size with GParted?GParted doesn't recognize the unallocated space after my current partitionWhat is the best way to add unallocated space located before to Ubuntu 12.04 partition with GParted live?I can't figure out how to extend my Arch home partition into free spaceGparted Linux Mint 18.1 issueTrying to extend but swap partition is showing as Unknown in Gparted, shows proper from fdiskRearrange partitions in gparted to extend a partitionUnable to extend partition even though unallocated space is next to it using GPartedAllocate free space to root partitiongparted: how to merge unallocated space with a partition