If I understand you correctly; the reason why you implemented this in PHP is because PHP is what you are good/best at?
Also excuse my limited ignorant knowledge about PHP, but my impression about PHP is that it is runs as an instance of the web server or something? (Please, correct me if I made any fundamental mistake here!) When it comes to perl vs PHP, I believe both of these languages are interpreted in the host evirionment, and I can't see any reason why there should be any significant performance difference between these two. On the other hand I can imagine an performance difference on doing this with C/C++, which would be my natural choose when writing a cmd line parser. > -----Original Message----- > From: Ignatius Reilly [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 11, 2003 5:09 PM > To: Svensson, B.A.T. (HKG) > Cc: Php Win32 list > Subject: Re: [PHP-WIN] reading lines from a file > > > Hi Anders, > > Well, of course the parser will consume full resources during several > minutes. But I trust our old fellow George would do the parsing on a > separate machine, and only do the LOAD DATA LOCAL on the production machine > at night or such. > > My question was more as to whether there is a fundamental performance > difference for file parsing between PHP at the command line and other > languages such as Perl (which I don't know, so you won't have the > opportunity to fire me because you won't hire me in the first place :-) > > Cheers > > Ignatius (self-employed idiot, currently pondering about firing himself) ____________________________________________ ----- Original Message ----- From: "Svensson, B.A.T. (HKG)" <[EMAIL PROTECTED]> To: "Ignatius Reilly" <[EMAIL PROTECTED]> Cc: "Php Win32 list" <[EMAIL PROTECTED]> Sent: Tuesday, February 11, 2003 4:12 PM Subject: RE: [PHP-WIN] reading lines from a file > > I trust that I am not the only one to be curious to > > learn more concerning your remark. > > [...] > > > Would you care to explain in more details why PHP is > > a MUST DON'T to do this? > > Hi, > > Thanx for your comment. > > One can talk about things like load balance for scalability, > and other boring subjects, but I agree that it is of course > hard to establish what is meant with a "good" design without > knowing the purposes. But, my general view goes this: > > "Of course you can use a hammer to nail a screw, but > a screw driver will do the job much easier and better." > > > ARGUMENT OF COUPLING & COHESION: > > By using for instance PHP for parsing a large text files, > you are stealing resources from the web server (assuming > PHP runs as an instance within Apache), resources better > used elsewhere for other purposes. > > A single application (the parser) can be executed in > its own processing space and given independent priority, > this will favoring parallelism with multi CPU system; > if the parser is smart enough written it might even > utilize several CPU's, possible running with low priority > as a background task. > > If the system become over loaded, then parser > application can easily be moved onto another system. > > Anyway, the main idea is that you wants to keep the > pears and apples separated from each other. > > By the way; You're fired! :) > > //Anders > -- PHP Windows Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
