On Wed, 2 May 2001, Chris McDonough wrote:
> The docs (available via the --help switch) go into some of this detail, but
> I agree that a narrative explaining how to approach it from a functional
> perspective would be a good thing.
This should go in the debuggin and testing chapter of the dev g
I'll vouch for the effectiveness of this method in tracking down some
problems. Chris' advice helped us track down some horrendous numbers around
a method calling DateTime. We've seen some definite improvements since we
reworked the way we're doing that function. It raises a question,
though--anyo
Hello Zope and ZODB users!
The folks at Digital Creations, PythonLabs bring to you the second
beta release of a Berkeley DB based storage for ZODB. Information
about the Berkeley storage, can be found on the Berkeley storage Wiki
at
http://www.zope.org/Wikis/ZODB/BerkeleyStorage
and other
The docs (available via the --help switch) go into some of this detail, but
I agree that a narrative explaining how to approach it from a functional
perspective would be a good thing.
- Original Message -
From: "Tim McLaughlin" <[EMAIL PROTECTED]>
To: "'Chris McDonough'" <[EMAIL PROTECTE
Nice info. This could be useful for many, many things. you oughtta put
this in a how-to (if you haven't already). thanks Chris.
I'll use it if we have any more issues. Currently, as I told ChrisW, the
issues have stopped. But I'm still keeping my eye on it.
-Original Message-
From: C
Chris McDonough wrote:
>
Thanks, that's just what I was looking for
> The goal is to indentify methods or requests that take a long time, don't
> return, or are accessed frequently.
Yup
> If you can match this data up with
> specific problems you've experienced (possibly by way of times/da
One of the more important bits is the "active" count when using
the --detailed option to requestprofiler. This tells you how many *other*
requests were "unfinished" at the end of a particular request.
So for instance, if you run requestprofiler like this:
python requestprofiler.py log.file.na
> > Attached is a script that I just checked into the trunk to do analysis
of
> > the file generated by the -M log. It can help you figure out if there's
a
> > pattern to the hangs (whether it happens on a particular method, whether
it
> > happens at heavy load time, whether it happens at a parti
Chris McDonough wrote:
>
> Absolutely! When you've got some representative data, and you've
> successfully run requestprofiler against it in various ways, let me know.
Hmmm, not really sure what I should be looking for :-S
What ways should I look to run it and what should I do with the output?
Hi,
i have found a solution in DT_In.py
change this( beginning at line 537 ):
else:
kw['previous-sequence']=0
if index==last:
try:
# The following line is a sneaky way
Chris McDonough wrote:
>
> Hmmm... it might be useful to turn on detailed request logging (-M logging)
> in the start file (see z2.py).
OK, this is done now...
> Attached is a script that I just checked into the trunk to do analysis of
> the file generated by the -M log. It can help you figure
Well, it's still happening, this time I was just browsing the management
interface :-(
The last thing in Z2.log was:
194.193.44.4 - - [02/May/2001:14:35:30 +0100] "GET
/VirtualHostBase/http/server.nipltd.com:80/VirtualHostRoot/manage_workspace
HTTP/1.0" 302 440 "http://www.cases.nipltd.com/manag
Chris McDonough wrote:
>
> But to make it happen you'd need ZPublisher to support a
> callback from ZServer when a connection was terminated.
> Since I know little about either, I'm not entirely confident
> I can be more specific.
yeah, well, even I was impressed how high above my head that flew
Hi,
I have found a error/bug in the dtml-in tag.
I have an SQL-Query that returns traffic-data grouped by month and year.
Th SQL-query returns 5 rows of data.
I want a page to show only one month.
If i use:
.
I got the following result.
The next-statement returns the url to the next r
14 matches
Mail list logo
