TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Need a word for... From:Robert Lauriston <robert -at- lauriston -dot- com> To:"techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 4 Feb 2010 09:26:50 -0800
I've seen "thrashing" used in the context of processor load balancing.
On Thu, Feb 4, 2010 at 6:47 AM, Peter Neilson <neilson -at- windstream -dot- net> wrote:
> Partially on the road to an answer... "Thrashing" is the term for the
> situation in which a virtual-memory computer system (or one with some
> similar memory management scheme) spends nearly all its time managing
> memory (of which there is too little) and nearly none doing useful work.
>
> Indeed, my house is in a similar situation. The usual method for
> cleaning things up is to move everything from one room into another and
> clean the one, throwing trash out in the process. It does not work when
> all the rooms are already full.
>
> McLauchlan, Kevin wrote:
>> Once again, I'm turning to the Techwr-l "reverse-lookup-dictionary" for a term that I'm pretty sure exists, but which is eluding me at present.
>>
>> Is there a general, or engineering, term for a condition where something is dropped/stopped and retries/resumes, but it happens so frequently and rapidly that it's annoying (or a drag on resources)?
>>
>> It's not "jitter", but a word of that sort.
>>
>> It's not a "race condition" - two signals or events 'racing' each other to determine an outcome... but sorta in the neighborhood.
>>
>> With that said, here's the situation.
>>
>> Picture a group of networked devices in a High Availability cluster configuration. They take part in load balancing, and they synchronize constantly to back each other up, in the event that one or more fails in some way. Now imagine they're geographically dispersed. Now imagine that the internet trunk from one country is flaky. It goes in. It goes out. It has its good days. It has its bad days. But the result is that the clustered appliance that lives at the other end of it can sometimes be dropping out and rejoining a _lot_. Possibly to the point - if that network segment gets bad enough - that the unit is being dropped out even faster than it can rejoin (with all the necessary handshaking). So, perhaps the customers request a settable "rejoin delay", such that the member can be told to take a breather (of a specified length) before attempting to rejoin.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
