comment on

Before your question can be answered, first some measurements must be made: Where exactly is your script "slow"?

Is it in reading the XBase data or in writing it to the csv-file? Dumping the data into MySQL should be rather fast unless of course the csv file is so big you are getting memory problems.

If we are speaking of really huge amounts of data, it is probably better to load the data record by record and send them straight from the XBase database to the MySQL database. Shifting around the data through intermediary files will make your script IO-bound and as everything has to go back and forth several times on the same harddisk, you create a bottleneck in the IO.

CountZero

A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

In reply to Re: how can I make this faster by CountZero
in thread how can I make this faster by padawan_linuxero

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Do you know where your variables are?
	PerlMonks