wagsbags wrote:I work at a large office with a network supporting several thousand workstations, several networking drives etc.
notfred wrote:If you have good IT guys
d0g_p00p wrote:How do you support "several thousand workstations" yet you don't have admin rights?
wagsbags wrote:It's either 0, 14 or 20 seconds. Not 7, not 16. I've checked everything I can think of that windows monitors and nothing is happening during that time as far as I can tell. It's not pegging the CPU, hard drive, ram etc. This happens whether the file is on the network, or on the local drive. It doesn't matter how big the file is (though after the lag large files or programs will take a few seconds to load normally). It also happens when I open programs, right click any icons, or try to copy a file. It seems to be random whether it's 0, 14 or 20 seconds even if I do the same thing many times in a row.
thegleek wrote:d0g_p00p wrote:How do you support "several thousand workstations" yet you don't have admin rights?
Easy. He said he works at a place with the NETWORK supporting 1000s of users. I work in a similar workspace.
They install SOE images on our laptops and restrict our access even if we do have Administrative rights, kinda like a sudo without full access.
d0g_p00p wrote:My bad, I read that wrong.
Well, the context menu handlers are incomputron9000 wrote:As an aside lots of programs and things try to get added to the context menus in Windows. If even one of those is trying to hit a network-resource, that could explain the issues... if the client has no connection, just load the menu normally, but if the client is attached to a network, go try to grab it. And each could have their own time-outs.
The registry is cached; you wouldn't see consistent times between the first and second case, and it wouldn't take that long no matter what the "mess." Multi-second delays with consistent duration like that screams "hardware time-out" to me.computron9000 wrote:What surprised me was the idea of the consistency of the times. That seems registry related if accurate: why? because it would take roughly the same time to process the mess in there.
Users browsing this forum: Bing [Bot] and 2 guests