|Kat Wrote:I mean, I go to work for 8 hours. Conceivably, I can achieve X amount of work in that time.
However, it seems like every time I plan to spend a whole day attacking my filing, someone needs me to scan something and somebody calls and somebody's looking for a file and somebody needs something typed and somebody needs their printer fixed and the Orkin guy shows up and needs to be taken around, etc. Certainly that loads down MY processor, but it doesn't mean time passes any more slowly... just means I get less done in a day than I could if all that extra stuff wasn't going on, because unfortunately, time itself doesn't change. Even if my perception of it might. Ten minutes at the dentist SEEMS like an hour, while ten minutes having fun SEEMS like two minutes, but they're both still ten minutes regardless of how I perceive them to go. Am I totally missing the point?
Oh my, I went through a head trip trying to understand your point of view, but I got it and I can safely say you're missing the point. I see how easy it is to commit logical fallacies with this topic though.
In the real world, time is constant, and in order to reconcile the inaccuracies of your mental clock with reality, you need empirical means to measure time as an absolute, not relative unit. Time is time, as you say.
However on the Grid, the "mental clock" is a shared
system resource, and perception *is* reality. Consider the following:
- A CPU's performance is finite and constant
- Real time, and subsequently clock cycles, are constant
- Number of programs providing instructions is variable
- Number and complexity of instructions is variable
Therefore the following can be inferred:
- A CPU will process an equal amount of instructions each cycle, in exactly the same amount of real time.
- Because amount of instructions is variable, when total system load increases, each program has its instructions processed at a slower rate. The slowdown is systemic, affecting every process, but programs whose resource demands remain unchanged from previous cycles now find that their task takes more cycles to complete for no apparent reason. Schedules can't be kept in realtime.
Conclusion: The relevance of real time clock cycles is diminished.
To put this back into perspective vis a vis your personal experience with time - Imagine it's an unusually busy day at the office. You come in in the morning and begin performing a simple task that usually takes an hour, but the hands in the clock on your desk are spinning like a pinwheel and it's now 11pm. Funny, that felt like an hour to you. You look out the window and see the sun is still up even though it should be night. Everyone in the building is freaking out because surely, they should have accomplished more in those 14 hours that just flew by, right?
Bit of a trip, isn't it?