[NTLUG:Discuss] OT Perl vs C question

[Paul Ingendorf]

WOW! You could defiantly benefit from some optimization, or it is time to
invest in new hardware.  I've run a database with millions of monthly
financial transactions running queries with multiple joins, calculating:
reversals, chargebacks, splits, interchange, surcharge and totals for all
the transactions took less that 30 seconds on an AMD xp 1800 with 512MB RAM.
That was running yearly totals too.  The monthly settlements where much
quicker.

BTW, sometimes it isn't the query that needs optimization make sure you are
indexing the fields used in the queries and it should improve your life
drastically.  Think about it, if google can index the entire "visible
internet" and return results to your queries quicker than your browser can
render the page you should be able to run your queries in much less than 24
hours.

-----Original Message-----
From: discuss-bounces at ntlug.org [mailto:discuss-bounces at ntlug.org]On
Behalf Of Fred James
Sent: Tuesday, April 26, 2005 7:44 PM
To: alb at chrisalbertson.com; NTLUG Discussion List
Subject: Re: [NTLUG:Discuss] OT Perl vs C question

Chris Albertson
Admitting that I should not be considered a prize SQL programmer, I have
relied upon our SQL developers to produce as efficient a query as
possible.  That said ...

Evil flat files not withstanding, the SQL has been tested and it runs
for over 24 hours to acquire a 30 days range of data (that test run
being on a weekend, which is non-peak hours for us).  Our final run must
collect a 365 days range of data - estimated running time for the SQL
would therefore be about 304 hours (12.67 days)  We were kind of hoping
to run this query at least once a week, if not daily.

All sad, but true.
Regards
Fred James

--
Compassion alone stands apart from the continuous traffic between good and
evil proceeding within us.  "Om Mani Padme Hum"