Hiya Bill.
>> I found that the database we use is expensive when it comes to
>> preparing statements and it has bugs when prepared statements are
>> reused (why else would you use prepared statements ;-)).
>>
>
> You mean you created one big SQL call with JOINs and shit? If so, would
> you be
Kevin Conner wrote:
load group actually worked to improve your performance? Do you have
BLOBs or something? I don't see this with my specj benches.
I found that the database we use is expensive when it comes to
preparing statements and it has bugs when prepared statements
are reused (why el
> load group actually worked to improve your performance? Do you have
> BLOBs or something? I don't see this with my specj benches.
I found that the database we use is expensive when it comes to
preparing statements and it has bugs when prepared statements
are reused (why else would you use pre
load group actually worked to improve your performance? Do you have
BLOBs or something? I don't see this with my specj benches.
Bill
Kevin Conner wrote:
I am missing something or is my understanding of Commit options flawed?
I moved our app from B to A, added a new load group strategy and i
Phil Shrimpton wrote:
On Thursday 06 November 2003 22:51, Bill Burke wrote:
Hi,
As this app 'owns' its own database and the DB is not that quick, I
though that changing from the default commit option B to A should give me
some improvements, but seems to make no difference.
Are you doing a lot o
On Thursday 06 November 2003 22:51, Bill Burke wrote:
Hi,
> > As this app 'owns' its own database and the DB is not that quick, I
> > though that changing from the default commit option B to A should give me
> > some improvements, but seems to make no difference.
>
> Are you doing a lot of finder
> I am missing something or is my understanding of Commit options flawed?
I moved our app from B to A, added a new load group strategy and it flies.
It achieved a 90% speedup in our app.
The best way to see what is happening is to enable the cmp debugs and the
ReadAheadCache info (yes we're still
Are you doing a lot of finder queries? Finder queries still go to DB
except for findByPrimaryKey. Also, do you have a lot of contention?
Concurrent access? Take a look at the for-pay docs on how to optimize this.
Bill
Phil Shrimpton wrote:
Hi,
I am tuning an app before deployment on 3.2.2.
Hi,
I am tuning an app before deployment on 3.2.2.
As this app 'owns' its own database and the DB is not that quick, I though
that changing from the default commit option B to A should give me some
improvements, but seems to make no difference.
My tests complete in the same time with both opti
