[Zope] stability of zope?
Meilicke, Scott
scott.meilicke@intp.com
Thu, 13 Dec 2001 09:13:48 -0800
I think it is counting uptime and downtime in terms of seconds(or some sort
of time measurement). So if the total time the server has been running is
100 hours, and it was down for 3 one hour periods, then uptime would be
reported as 4 days, 1 hour (97 hours total). Downtime would be 3 hours. I
agree, there were 1-3 days where services were interrupted in this example.
So this uptime stat I ran does consider a reboot downtime, but measures time
more granularly than days.
This box is an Intranet server, so netcraft is not appropriate. You can
assume however, that the uptime is no better than these stats, as this is
the OS, and the service may have had difficulties of its own, including
planned downtime (restarting zope for product installs, bad python programs
gone bad, etc.)
-----Original Message-----
From: Stephan Goeldi [mailto:stephan_goeldi@hotmail.com]
Sent: Thursday, December 13, 2001 3:28 AM
To: scott.meilicke@intp.com; stephan.goeldi@datacomm.ch;
kosh@aesaeion.com; rene@xs4all.nl
Cc: zope@zope.org
Subject: RE: [Zope] stability of zope?
>Partial output from uptime:
>
>Since 4/24/2000:
>
> System Availability: 99.8800%
> Total Uptime: 596d 0h:2m:30s
> Total Downtime: 0d 17h:10m:56s
> Total Reboots: 32
> Mean Time Between Reboots: 18.65 days
> Total Bluescreens: 0
If you have 32 reboots in 596 days, then the uptime is not 596 days. The
line "Mean Time Between Reboots" states, that the average uptime is 18.65
days. So this stat doesn't think that a reboot is downtime. What says
www.netcraft.com about your uptime?
Stephan
http://www.zopehosting.ch
_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com
The information contained in this email message may be privileged and is
confidential information intended only for the use of the recipient or any
employee or agent responsible for delivering it to the intended recipient.
Any unauthorized use, distribution or copying of this information is
strictly prohibited and may be unlawful. If you have received this
communication in error, please notify the sender immediately and destroy the
original message and all attachments from your electronic files.