Speaking about AVX, I'd like to advise to pay more attention to CPU temperatures. Some CPUs have a sort of erratum, which can cause them to exceed the designed TDP when running certain AVX workloads.
This is also the reason why later CPU generations run AVX code at lower frequencies (usually by a few 100 MHz) than the original maximum non-turbo clock.
Mumak hi, I missed this post earlier.
My i5-4690K (yes it is a K and yes i confess, it is a little over clocked) had it's first panic after stopping all the usual GPU tasks and running 4 AVX tasks. The CPU temp reported 70C just before the panic, which is close to the limit suggested here Intel i5-4690K
You mentioned some generations with more likely a problem, can you give a reference list?
I completed 4 version 1.02 tasks (239717102, 239717368, 239717298, 239717062). They all are marked as "validation inconclusive" and the third task for the workunit remains unsent. Any chance it is being sent at all? Will I get any credits for them?
That host is using a 32bit app which (from some reports) seems quite a bit slower than a 64bit app.
Unfortunately, the Intel page for that CPU shows it supports SSE4.2 but not AVX. The applications page here lists only two apps for Windows at the moment, X86 and AVX. I guess that's why you don't have a 64bit app. I guess there could be quite a few Windows machines in your predicament so perhaps the Devs will soon release a 64bit non-AVX version for Windows at some point soon.
That host is using a 32bit app which (from some reports) seems quite a bit slower than a 64bit app.
hmm, I'm not 100% clear if this is true for all hosts. Just starting to get some valids in my i3-530
Probably a bit early to draw the conclusions on versions 1.03 and earlier apps, and we need to get some valids on 1.04. I'm also changing the CPU / GPU balance on my hosts so some fine tuning yet.
Quote:
The applications page here lists only two apps for Windows at the moment, X86 and AVX.
It's not clear to me on the application page what does "1.04 (X64)" mean compared to just "1.04".
(AVX) is clear, as is (SSE2), and I note (X64) tasks flagging SSE2, so am i correct in saying these should be (X64-SSE2) or just (SSE2) ?
I think it would be helpful in general on the application page to highlight (32bit OS) where appropriate. Edit: (show "32 bit" in the platform column)
It's not clear to me on the application page what does "1.04 (X64)" mean compared to just "1.04".
Those two are Linux apps. The first of the two Windows apps (1.04 SSE2) has Windows/x86 for the platform which means a 32bit app. The second of the two Windows apps is certainly a 64bit app but I took the (AVX) to mean that the app would only be sent to AVX capable hosts. From the way the Linux apps are labeled, I imagined there should be a (X64) app as well for those 64bit CPUs that don't have AVX.
It's not clear to me on the application page what does "1.04 (X64)" mean compared to just "1.04".
Those two are Linux apps. The first of the two Windows apps (1.04 SSE2) has Windows/x86 for the platform which means a 32bit app. The second of the two Windows apps is certainly a 64bit app but I took the (AVX) to mean that the app would only be sent to AVX capable hosts. From the way the Linux apps are labeled, I imagined there should be a (X64) app as well for those 64bit CPUs that don't have AVX.
There is a X64 app running on my Opteron 1210 with 64-bit SuSE Linux.
Tullio
It's not clear to me on the application page what does "1.04 (X64)" mean compared to just "1.04".
Those two are Linux apps. The first of the two Windows apps (1.04 SSE2) has Windows/x86 for the platform which means a 32bit app. The second of the two Windows apps is certainly a 64bit app but I took the (AVX) to mean that the app would only be sent to AVX capable hosts. From the way the Linux apps are labeled, I imagined there should be a (X64) app as well for those 64bit CPUs that don't have AVX.
I'm not sure i understand - There are three 64 bit Linux apps (typo maybe)?
Quote:
[pre]Linux running on an AMD x86_64 or Intel EM64T CPU 1.04 19 Feb 2016, 16:30:35 UTC
Linux running on an AMD x86_64 or Intel EM64T CPU 1.04 (AVX) 19 Feb 2016, 16:30:35 UTC
Linux running on an AMD x86_64 or Intel EM64T CPU 1.04 (X64) 19 Feb 2016, 16:53:47 UTC[/pre]
T'is cool Bernd. We are all
)
T'is cool Bernd. We are all eager. :-)
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
RE: RE: AVX tasks crash
)
Yes, that is the Windows 10 PC with its A10 6700 which should have AVX enabled.
Tullio
RE: Speaking about AVX, I'd
)
Mumak hi, I missed this post earlier.
My i5-4690K (yes it is a K and yes i confess, it is a little over clocked) had it's first panic after stopping all the usual GPU tasks and running 4 AVX tasks. The CPU temp reported 70C just before the panic, which is close to the limit suggested here Intel i5-4690K
You mentioned some generations with more likely a problem, can you give a reference list?
I completed 4 version 1.02
)
I completed 4 version 1.02 tasks (239717102, 239717368, 239717298, 239717062). They all are marked as "validation inconclusive" and the third task for the workunit remains unsent. Any chance it is being sent at all? Will I get any credits for them?
"Why some hosts take 6h and
)
"Why some hosts take 6h and some 24h we don't know yet."
Only to let you know (I know you are working on it):
ID: 12087505: extremely long processing time
Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz [Family 6 Model 26 Stepping 5]
(8 Prozessoren)
Arthur
I know I am a part of a story that starts long before I can remember and continues long beyond when anyone will remember me [Danny Hillis, Long Now]
That host is using a 32bit
)
That host is using a 32bit app which (from some reports) seems quite a bit slower than a 64bit app.
Unfortunately, the Intel page for that CPU shows it supports SSE4.2 but not AVX. The applications page here lists only two apps for Windows at the moment, X86 and AVX. I guess that's why you don't have a 64bit app. I guess there could be quite a few Windows machines in your predicament so perhaps the Devs will soon release a 64bit non-AVX version for Windows at some point soon.
Cheers,
Gary.
RE: That host is using a
)
hmm, I'm not 100% clear if this is true for all hosts. Just starting to get some valids in my i3-530
Probably a bit early to draw the conclusions on versions 1.03 and earlier apps, and we need to get some valids on 1.04. I'm also changing the CPU / GPU balance on my hosts so some fine tuning yet.
It's not clear to me on the application page what does "1.04 (X64)" mean compared to just "1.04".
(AVX) is clear, as is (SSE2), and I note (X64) tasks flagging SSE2, so am i correct in saying these should be (X64-SSE2) or just (SSE2) ?
I think it would be helpful in general on the application page to highlight (32bit OS) where appropriate. Edit: (show "32 bit" in the platform column)
RE: It's not clear to me on
)
Those two are Linux apps. The first of the two Windows apps (1.04 SSE2) has Windows/x86 for the platform which means a 32bit app. The second of the two Windows apps is certainly a 64bit app but I took the (AVX) to mean that the app would only be sent to AVX capable hosts. From the way the Linux apps are labeled, I imagined there should be a (X64) app as well for those 64bit CPUs that don't have AVX.
Cheers,
Gary.
RE: RE: It's not clear to
)
There is a X64 app running on my Opteron 1210 with 64-bit SuSE Linux.
Tullio
RE: RE: It's not clear to
)
I'm not sure i understand - There are three 64 bit Linux apps (typo maybe)?
The first and third apps I am referring to.