Stephan Richter wrote at 2005-10-13 08:08 -0400:
>On Thursday 13 October 2005 07:02, Tarek Ziadé wrote:
>> sub part:
>> For zodb objects, i was wondering if we could somehow size what's beeing
>> pickled, since it's just a buffer.
>> we could therefore measure the size of what's beeing serialized i
>> I suggest to extend the approach by adding monitoring of the resident
>> memory occupied by the process, alongside the execution time. Zope 3 is a
>> rather huge beast, doing all the things it does.
> Can this be *reliably* done on all platforms? In other words, is there a
> *reliable* Python
Stephan Richter wrote:
On Wednesday 12 October 2005 16:20, Benji York wrote:
>>> browser.open('http://localhost/foo')
>>> browser.last_request_time < 0.5
I wonder how useful performance tests are to testbrowser, because over time we
might add new features that naturally slow it down.
Chris Withers wrote:
Tarek Ziadé wrote:
I think the only reliable way is to write a new python debugger.
What does pdb have to do with it?
Sorry i mistyped, i meant a python debug build, to get all objects instances
Tarek
___
Zope3-dev mailing
Tarek Ziadé wrote:
I think the only reliable way is to write a new python debugger.
What does pdb have to do with it?
cheers,
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
___
Zope3-dev
On Thursday 13 October 2005 07:02, Tarek Ziadé wrote:
> sub part:
> For zodb objects, i was wondering if we could somehow size what's beeing
> pickled, since it's just a buffer.
> we could therefore measure the size of what's beeing serialized in a test.
> that's a measure, but i wonder if it can t
Stephan Richter wrote:
On Wednesday 12 October 2005 17:53, Nicola Larosa wrote:
I suggest to extend the approach by adding monitoring of the resident
memory occupied by the process, alongside the execution time. Zope 3 is a
rather huge beast, doing all the things it does.
Can this be
On Wednesday 12 October 2005 16:20, Benji York wrote:
> 2) testbrowser should keep up with a (machine-independent) metric of how
> long the previous request took so performance assertions can be made
> inside tests. E.g.
>
> >>> browser.open('http://localhost/foo')
> >>> browser.last_req
On Wednesday 12 October 2005 17:53, Nicola Larosa wrote:
> I suggest to extend the approach by adding monitoring of the resident
> memory occupied by the process, alongside the execution time. Zope 3 is a
> rather huge beast, doing all the things it does.
Can this be *reliably* done on all platfor
> Tarek has started some very interesting work on adding performance
> testing to the Zope 3 testing infrastructure and it so happens that Jim
> and I were discussing something very similar last week, so I'd like to
> suggest some functionality we might want to have (which I should be able
> to hel
On Wednesday 12 October 2005 16:20, Benji York wrote:
> 3) the functional testing framework should be extended to allow the
> collection of total time (again, machine-independent) per request and
> the test runner should have an option to display the top "n" slowest
> requests.
>
> Comments?
Tarek
11 matches
Mail list logo
