On Wed, Feb 16, 2005 at 09:44:08AM -0800, Jeff Zucker wrote :
[EMAIL PROTECTED] wrote:
Total Elapsed Time = 63.19465 Seconds
User+System Time = 43.46465 Seconds
Exclusive Times
%Time ExclSec CumulS #Calls sec/call Csec/c Name
66.5 28.91 36.463 109445 0.0003 0.0003
On Fri, Apr 01, 2005 at 03:09:12PM +0900, Charles Plessy wrote:
You may wonder the purpose of this mail, as there is no new
crucial information. The reason is that I do not like not knowing the
end of the story when I browse archived threads.
Thanks Charles.
Tim.
Charles Plessy wrote:
As I had better to spend my time on analysing some data with
my script rather than analysing the script itself, I eventually
swiched to DBI::SQLite, which solved my problem by performing the
query in a few seconds.
There's no question, SQLite is faster than DBD::CSV
On Thu, Feb 03, 2005 at 10:18:43AM +, Tim Bunce wrote :
On Thu, Feb 03, 2005 at 06:27:05PM +0900, [EMAIL PROTECTED] wrote:
Dear list,
I wrote a simple CGI script using DBD::CSV on a linux
computer, and then installed it on a iMac G5. Its execution time is
now alomst 10 times
On Thu, Feb 03, 2005 at 11:33:10AM -0800, Henri Asseily wrote :
Also note that DBD::CSV is significantly impacted by I/O speed. If your
IMac G5 has a 4200 rpm drive and your linux box has a 10k rpm one, that
makes quite a large difference.
Would that mean that running the script
On 2005-02-16 19:44:49 +0900, [EMAIL PROTECTED] wrote:
On Thu, Feb 03, 2005 at 10:18:43AM +, Tim Bunce wrote :
On Thu, Feb 03, 2005 at 06:27:05PM +0900, [EMAIL PROTECTED] wrote:
Dear list,
I wrote a simple CGI script using DBD::CSV on a linux
computer, and then installed it
From: Charles Plessy [EMAIL PROTECTED]
Date: 2005/02/16 Wed AM 04:58:36 CST
Would that mean that running the script twice should
dramatically accelerate the execution because the file would then be
cached in memory? (which does not work, I just tried).
Keep in mind that it's not just
On Feb 16, 2005, at 2:58 AM, Charles Plessy wrote:
On Thu, Feb 03, 2005 at 11:33:10AM -0800, Henri Asseily wrote :
Also note that DBD::CSV is significantly impacted by I/O speed. If
your
IMac G5 has a 4200 rpm drive and your linux box has a 10k rpm one,
that
makes quite a large difference.
[EMAIL PROTECTED] wrote:
Total Elapsed Time = 63.19465 Seconds
User+System Time = 43.46465 Seconds
Exclusive Times
%Time ExclSec CumulS #Calls sec/call Csec/c Name
66.5 28.91 36.463 109445 0.0003 0.0003 SQL::Statement::eval_where
I'm the maintainer of DBD::CSV and while I don't have time
On Wed, Feb 16, 2005 at 07:44:49PM +0900, [EMAIL PROTECTED] wrote:
As somebody kindly pointed me out that hardware differences
could have a strong impact on the results, I will suppose that this is
the reason why I have seen such speed inconsistencies, unless somebody
found something
Dear list,
I wrote a simple CGI script using DBD::CSV on a linux
computer, and then installed it on a iMac G5. Its execution time is
now alomst 10 times slower. Using print instructions, I traced the
bottleneck to the following instruction :
$sth-execute;
Now I am a bit stuck,
On Thu, Feb 03, 2005 at 06:27:05PM +0900, [EMAIL PROTECTED] wrote:
Dear list,
I wrote a simple CGI script using DBD::CSV on a linux
computer, and then installed it on a iMac G5. Its execution time is
now alomst 10 times slower. Using print instructions, I traced the
bottleneck to the
On Feb 3, 2005, at 2:18 AM, Tim Bunce wrote:
On Thu, Feb 03, 2005 at 06:27:05PM +0900, [EMAIL PROTECTED]
wrote:
Dear list,
I wrote a simple CGI script using DBD::CSV on a linux
computer, and then installed it on a iMac G5. Its execution time is
now alomst 10 times slower. Using print
13 matches
Mail list logo
