If you do not need to preserve the order in which you read the lines of your input for each make/model, then you could stuff all the data into a hash-of-hashes structure. This may be more of a memory hog than you can tolerate, but it certainly is faster on my machine than all those mkdir's and open/closes (I created an input file of 13 million lines): 
use strict;
use warnings;

# Read all input into data structure
my %cars;
my $i = 0;  # unique tag for hash keys
while (<>) {
    chomp;
    my ($make, $model, $rest) = split /,/, $_, 3;
    $cars{$make}{$model}{"$rest,$i"}++;
    $i++;
}

# Create each directory once
# Open/close each file once
my $out_dir = "/var/tmp/cars"; #Output directory for
for my $make (keys %cars) {
    my $dir = "$out_dir/$make";
    system "mkdir -p $dir";
    for my $model (keys %{ $cars{$make} }) {
        open my $fh, '>', "$out_dir/$make/$model" or die $!;
        for my $rest (keys %{ $cars{$make}{$model} }) {
            my @specs = split /,/, $rest, 2;
            print $fh (join ',', ($make, $model, @specs)), "\n";
        }
        close $fh;
    }
}

[download]

Update: On second thought, I think you can preserve input order by using an HoHoA instead of the HoHoH above. That should get rid of the smelly tag I introduced, too.

In reply to Re: handler performance question by toolic
in thread handler performance question by magawake

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.