WU's length
Message boards :
Number crunching :
WU's length
Message board moderation
Author | Message |
---|---|
Send message Joined: 10 Jul 13 Posts: 21 Credit: 10,363,957 RAC: 0 |
Last modified: 30 Nov 2014, 6:30:15 UTC Hello, could someone explain to me why there are so many changes in the WU's lenght ? Below instances = AVX, (all on the same machine - ID 54940 !) but same happens with SSE2 and SSE3 : ALL WU's need > 2x more time to complete than 4 or 5 days ago ... ? Thank You
|
Send message Joined: 17 Nov 14 Posts: 13 Credit: 6,630,897 RAC: 1,792 |
I also notice a recent (approximate) double in run times. But when I look back farther in the logs I see that in early November the "short" runs began to replace "long" runs that had been typical up to that time. So, in effect, the WU size seems to have reverted back to a previous value. Who knows what the "right" size is? I just assumed it is something inherent in the batches of work that are distributed.
|
Send message Joined: 1 Jan 14 Posts: 302 Credit: 32,696,384 RAC: 2,320 |
I also notice a recent (approximate) double in run times. But when I look back farther in the logs I see that in early November the "short" runs began to replace "long" runs that had been typical up to that time. So, in effect, the WU size seems to have reverted back to a previous value. Who knows what the "right" size is? I just assumed it is something inherent in the batches of work that are distributed. Longer units also means less times we users have to connect to the Project Servers, they have been overloaded at times so this could be a return to the longer units to help solve the problem. |
Message boards :
Number crunching :
WU's length