Martijn Pieters wrote:
On 11/24/06, Yuri <[EMAIL PROTECTED]> wrote:
8.7971 was the time without subtransactions, 2.3 with.
Ops... -.-
Indeed. And if you tweak the threshold as Jonathan suggested, you
could even get it lower.
Just to clarify, 2.3 sec is the time to insert only one object :)
On 11/24/06, Yuri <[EMAIL PROTECTED]> wrote:
8.7971 was the time without subtransactions, 2.3 with.
Ops... -.-
Indeed. And if you tweak the threshold as Jonathan suggested, you
could even get it lower.
--
Martijn Pieters
___
Zope maillist - Zope@z
Martijn Pieters wrote:
On 11/24/06, Yuri <[EMAIL PROTECTED]> wrote:
> and *enable* subtransactions!
When I have a transaction wich takes almost 1 sec, I don't think it will
change anything :) I'll try CallProfiler :)
Did you try? Subtransactions are not the same as transactions. They
are an
Martijn Pieters wrote:
On 11/24/06, Yuri <[EMAIL PROTECTED]> wrote:
> and *enable* subtransactions!
When I have a transaction wich takes almost 1 sec, I don't think it will
change anything :) I'll try CallProfiler :)
Did you try? Subtransactions are not the same as transactions. They
are an o
On 11/24/06, Yuri <[EMAIL PROTECTED]> wrote:
> and *enable* subtransactions!
When I have a transaction wich takes almost 1 sec, I don't think it will
change anything :) I'll try CallProfiler :)
Did you try? Subtransactions are not the same as transactions. They
are an optimization, so try them
Yuri wrote:
When I have a transaction wich takes almost 1 sec, I don't think it will
change anything :)
You might be surprised...
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
___
Zope m
Andreas Jung wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On 24. November 2006 11:20:39 +0100 Andreas Jung <[EMAIL PROTECTED]> wrote:
ZopeProfiler will tell you about bottlenecks.
Doesn't work in zope 2.6 based on python 2.1 :(
Try CallProfiler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On 24. November 2006 11:20:39 +0100 Andreas Jung <[EMAIL PROTECTED]> wrote:
>>
>>>
>>> ZopeProfiler will tell you about bottlenecks.
>>>
>>
>> Doesn't work in zope 2.6 based on python 2.1 :(
>>
>
> Try CallProfiler instead.
>
and *en
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On 24. November 2006 11:16:50 +0100 Yuri <[EMAIL PROTECTED]> wrote:
>>>
>>>
>>
>> ZopeProfiler will tell you about bottlenecks.
>>
>
> Doesn't work in zope 2.6 based on python 2.1 :(
>
Try CallProfiler instead.
- -aj
- --
ZOPYX Ltd. & Co. K
Andreas Jung wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On 23. November 2006 17:07:39 +0100 Yuri <[EMAIL PROTECTED]> wrote:
Hi!
I've an old machine with zope 2.6 with an application based on ZClass.
Now, updating 4000 record takes ages (more than an hour...), basically it
Jonathan wrote:
- Original Message - From: "Yuri" <[EMAIL PROTECTED]>
To:
Sent: Thursday, November 23, 2006 11:07 AM
Subject: [Zope] help performance
Hi!
I've an old machine with zope 2.6 with an application based on
ZClass. Now, updating 4000 record takes ag
- Original Message -
From: "Yuri" <[EMAIL PROTECTED]>
To:
Sent: Thursday, November 23, 2006 11:07 AM
Subject: [Zope] help performance
Hi!
I've an old machine with zope 2.6 with an application based on ZClass.
Now, updating 4000 record takes ages (more than a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- --On 23. November 2006 17:07:39 +0100 Yuri <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I've an old machine with zope 2.6 with an application based on ZClass.
> Now, updating 4000 record takes ages (more than an hour...), basically it
> is a propertyshee
Hi!
I've an old machine with zope 2.6 with an application based on ZClass.
Now, updating 4000 record takes ages (more than an hour...), basically
it is a propertysheet update + recatalog of every object of 4000.
Can I have significative performance upgrade changing something in the
code base
14 matches
Mail list logo