Re: performance - loops, sub refs, symbol tables, and if/elses

[krazken]

You have 3 perl programs...

first one...reads the data and decides which program to send the data to.
second program...does the apple transformations and the apple database stuff
third program...does the banana transformations and the banana database stuff.


Why break it up like this you ask?? Well, you don't have to, but where I am going with this is that the first program can fork off a process and call either the second or third program..and assuming your database can handle multiple transactions at once, you shouldn't be in any trouble from that point. Plus this method would allow you to work over multiple processors on the server to get the maximum performance out of it. Also, from a maintability standpoint, you know you have an apple program and a banana program, so if you have to change the apple logic, you don't have to sift through extraneous code looking for it.

Just a thought. later.
krazken