disabling of interruptsto preventcontext switching US9098270
people switching between teams(passive) is also caused byContext switching
the M - interface and the R - interface(passive) is thus caused byContext - switching
In short , a 10ms timeslicing green thread scheduler would be possible in a C extension or through specific Ruby scriptsto preventcontext switching at all
the productivity loss(passive) caused bythe productivity loss
the lost productivity(passive) caused bythe lost productivity
more frustration and stress ... than any perceived productivity gainscausesmore frustration and stress ... than any perceived productivity gains
you to get less done overall and , what you do get done , gets done more slowly and with less qualitycausesyou to get less done overall and , what you do get done , gets done more slowly and with less quality
some delays with CPU at 100 %was causingsome delays with CPU at 100 %
brain damage brain damage is well documented that multitasking kills productivitycausesbrain damage brain damage is well documented that multitasking kills productivity
a loss in developer productivitycausesa loss in developer productivity
to an up to 40 % decline in productivitycan ... leadto an up to 40 % decline in productivity
up and manage an effective schedule needs to be blended with the ability to be flexible to shifting client and team needsto setup and manage an effective schedule needs to be blended with the ability to be flexible to shifting client and team needs
a large amount of waste ... often estimated to be around 20 % ( example belowcreatesa large amount of waste ... often estimated to be around 20 % ( example below
the problem with undeterministic timing(passive) resulted bythe problem with undeterministic timing
in non - acceptable response timeresultingin non - acceptable response time
to frustration and the inevitable loss of talentleadingto frustration and the inevitable loss of talent
inefficiency and the potential for poor customer servicecreatesinefficiency and the potential for poor customer service
from the default behaviour of the time - share ( TS ) schedulerresultsfrom the default behaviour of the time - share ( TS ) scheduler
to a 15 - 20 % time loss when you change tasks or contextsleadsto a 15 - 20 % time loss when you change tasks or contexts
tasks to get extended beyond the actual time neededalso causestasks to get extended beyond the actual time needed
from 5 to 30 minutes of wasted time per taskcan causefrom 5 to 30 minutes of wasted time per task
to a 15 - 20 percent time loss when you change tasks or contextsleadsto a 15 - 20 percent time loss when you change tasks or contexts
inefficiencies This “ thrashing ” between stories resulted in regular context switching , with the inefficiencies this producescreatesinefficiencies This “ thrashing ” between stories resulted in regular context switching , with the inefficiencies this produces
to unpredictable behaviorcan leadto unpredictable behavior
A Context , DemonstrationCreatingA Context , Demonstration
the randomization(passive) caused bythe randomization
OCports to change their state / signal on their owncausesOCports to change their state / signal on their own
multiple setup times and is very inefficient on the mindcausesmultiple setup times and is very inefficient on the mind
the page faultswas causingthe page faults
Slowdown(passive) is probably caused bySlowdown
I think(passive) is caused byI think
wastes(passive) caused bywastes
the brain to reorient itself to the current task at handcausesthe brain to reorient itself to the current task at hand
the amount of disruption(passive) caused bythe amount of disruption