• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

S@H data server down

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Originally posted by: Jeff7181
Little off topic.
Noticed it says i386 command line... wouldn't it be beneficial for it to make use of MMX or SSE or 3DNow instructions?

I believe i386 just means it's 32-bit (386 was the first 32-bit x86 CPU). S@H does indeed make use of MMX/SSE/3dnow, if I recall correctly.

On a side note: is the server still down? I've been having trouble submitting WUs on and off since it went down a few days ago. My cache will only last me a couple more days too so I hope this doesn't go on for too long.
 
Originally posted by: Flyermax2k3
Originally posted by: Jeff7181
Little off topic.
Noticed it says i386 command line... wouldn't it be beneficial for it to make use of MMX or SSE or 3DNow instructions?

I believe i386 just means it's 32-bit (386 was the first 32-bit x86 CPU). S@H does indeed make use of MMX/SSE/3dnow, if I recall correctly.

On a side note: is the server still down? I've been having trouble submitting WUs on and off since it went down a few days ago. My cache will only last me a couple more days too so I hope this doesn't go on for too long.

Looking at the log file on my Q I have had intermittent problems connecting but I've been able to keep my levels up.If you run criticaly low I suggest you contact 1 of the public Q operators in the SETIQ thread🙂

Btw SETI does not use MMX,SSE or 3DNow ,they could implement it but they have plenty of power available as it is so theres real need to.Also they have been (& are) busy with S@H2.
In the past their server bandwidth was a limiting factor to crunching power so optimising the clients would of only made that situation worse
 
Back
Top