MOO-cows Mailing List Archive
Re: FUP and LAG
Could it be .... your implementation?
The package itself is actually quite useful, when not done over-the-top.
It caused lag at river for a few weeks until we tracked it down to a huge
amount of fileread() calls. We re-implemented those calls with better
code and voila! Problem solved.
aka: barrett && archwizard @ rivermoo
On Wed, 26 Feb 1997, Edward L. Haletky wrote:
> Date: Wed, 26 Feb 1997 13:31:21 -0800 (PST)
> From: Edward L. Haletky <email@example.com>
> To: MOO-Cows@parc.xerox.com
> Subject: FUP and LAG
> Just a quick note to let you all know that FUP is BAD. We thought it could
> be very useful but it ended up costing us nearly a diskdrive, a few machine
> crashes, and huge amount of lag when being accessed.
> So we ripped it out this AM. Only thing FUP'd now is our Help.
> Best regards,
> Edward L. Haletky, President BATS (ISP Billing and Tracking System)
> AstroArch Consulting, Inc. http://www.tpoint.net/astroarch
- FUP and LAG
- From: "Edward L. Haletky" <firstname.lastname@example.org (none)>
Subject Index |