in reply to Re^2: Performance Trap - Opening/Closing Files Inside a Loop
in thread Performance Trap - Opening/Closing Files Inside a Loop

tmoertel,
I had thought about this myself after posting. The reason I didn't give it a lot of initial thought is because the Java developer made it clear that I was not welcome in the sandbox. My guess is that some sort of limited buffer would be best since that's still a whole lot of lines to be keeping all in memory.

Cheers - L~R

  • Comment on Re^3: Performance Trap - Opening/Closing Files Inside a Loop

Replies are listed 'Best First'.
Re^4: Performance Trap - Opening/Closing Files Inside a Loop
by Rhandom (Curate) on Dec 10, 2004 at 16:23 UTC
    If that is the case - combine the two methods.
    1. Buffer the strings up to say 10k or more.
    2. Once they hit that size - look for an open, or cache a new filehandle.
    3. Print out the buffered string for the file and clear the buffer.
    4. Finish off by flushing remaining buffers.
    my @a=qw(random brilliant braindead); print $a[rand(@a)];
[reply]

In Section Seekers of Perl Wisdom