Subject | Re: [firebird-support] Re: Firebird Usage Load Problem |
---|---|
Author | Jakub Hegenbart |
Post date | 2005-07-15T03:21:43Z |
On Friday 15 of July 2005 02:25, Maurice Ling wrote:
remember correctly that VARCHARs get transmitted in their full length? - and
pushing it back and committing each row separately might be a partial cause
of your trouble. Aren't those VARCHARs partially empty?
And we still don't know (I, for one, haven't been able to grasp your problem
in its entirety yes) the data volumes, the nature of what you call
"processing raw text", table structures and queries and so on. Difficult to
advice anything...
If you are not willing to rewrite your scripts for MySQL to make a comparison,
which you are not willing to do, IIRC, you probably should concentrate more
on solving your problems in a different, less resource-expensive way. I'm
sure there is one.
The last conclusion might also be that you're simply processing much data in a
complicated way and that it simply can't be helped just because it is much
processing you can't avoid, but I'm sure there is still a lot to be improved,
at least the "commit after each line" and "VARCHAR(18000)" symptoms indicate
that...
Jakub Hegenbart
> There are a few reasons why my system administrator is agitated.Your scripts, for example? Pushing VARCHAR(18000) through TCP/IP stack - do I
>
> 1. He's a mysql user and is very used to seeing database processes
> using low CPU. So, to that is, why is FB using >90% CPU while mysql is
> <10% CPU? If DBMS is by nature of the beast CPU intense, shouldn't
> both be as intense? So what is different here?
remember correctly that VARCHARs get transmitted in their full length? - and
pushing it back and committing each row separately might be a partial cause
of your trouble. Aren't those VARCHARs partially empty?
And we still don't know (I, for one, haven't been able to grasp your problem
in its entirety yes) the data volumes, the nature of what you call
"processing raw text", table structures and queries and so on. Difficult to
advice anything...
If you are not willing to rewrite your scripts for MySQL to make a comparison,
which you are not willing to do, IIRC, you probably should concentrate more
on solving your problems in a different, less resource-expensive way. I'm
sure there is one.
The last conclusion might also be that you're simply processing much data in a
complicated way and that it simply can't be helped just because it is much
processing you can't avoid, but I'm sure there is still a lot to be improved,
at least the "commit after each line" and "VARCHAR(18000)" symptoms indicate
that...
Jakub Hegenbart