Perl vs Java for specific task

Discussion in 'Perl' started by John Smith, Aug 30, 2004.

  1. John Smith

    John Smith Guest


    I have a rather odd question. My company is an all java/oracle shop.
    We do everything is Java... no matter what it is... parsing of text
    files, messaging, gui you name it. My question is this... is Perl so
    much better at parsing text files and outputing that we would see a
    substantial speed increase? We process about 10 million records in
    flat files a day for reformatting before putting them in a DB.

    Also, when it comes to Unix threading... which one would be better off
    Java or perl? Essentially, we would break the 10 million down into 10
    files... each file is done in a seperate thread... The program also
    has to keep a hashmap of keys to make sure we don;t include duplicate
    records and it must connect to oracle every once in a while... is
    switching to perl worth it considering the investment and know how we
    have in java? This is the only portion of the code we would consider
    switching to perl...



    John Smith, Aug 30, 2004
    1. Advertisements

  2. John Smith

    nobull Guest

    AFIAK most Java implementations have a much better threading
    implementation than is found in Perl5. This is becase Java was
    designed to be threaded from day-0. In Perl threading is very much an

    Up until Perl5.8 Perl's threading was essentially useless and even now
    you are usually better using forks than threads on Perl.
    A Perl programmer could possibly write a solution using 10 separate
    processes that would outperform a Java solution. But no even as a fan
    of Perl I wouldn't say this alone was sufficient justification to
    learn Perl.

    This newsgroup does not exist (see FAQ). Please do not start threads
    nobull, Aug 31, 2004
    1. Advertisements

  3. John Smith

    penguinista Guest

    Yes, I'd think perl is that much better, it's designed for parsing text
    data. It also uses a runtime model that tends to use higher level
    operations, spending less time interpreting the model and more doing
    work. As opposed to JRE which uses a low level byte code. Not to
    mention that someone who knew the language could generate the parsing
    code in perl faster and easier than in java.
    Is the multithreaded design inherant to the problem or part of a java
    style solution, as in watching multiple input files? While perl is weak
    at multithreading, it is very good at not needing to multithread. An
    optimal solution in perl would probably be structured differently than
    an optimal solution in java.
    penguinista, Sep 1, 2004
  4. John Smith

    John Smith Guest

    Okay, I have heard this before... but what I need to do is this. I
    need to parse 4 or 5 delimited text files that have between one and
    two million records in them each. Now. I was thinking it would be
    best to use perl because then I don't have the overhead of the JVM and
    from my past memory perl was ALWAYS the choice for text parsing.
    However, as you suggested... perl was not written originally to be
    multithreaded.... so will launching > 1 perl program off in seperate
    threads be a problem or is it simply that a single multi-threaded perl
    application has issues?

    Well, I will take your statement into account... it seems as though it
    might be worth looking into doing it in java as well. Any more tips
    or info?
    John Smith, Sep 6, 2004
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.