Originally posted by HCT+23 January 2004 - 21:20-->QUOTE (HCT @ 23 January 2004 - 21:20)
wt are u confused about? [/b]
[11:15:22] Finished a frame (209)
[11:21:43] Finished a frame (210)
[11:27:39] Finished a frame (211)
[11:33:32] Finished a frame (212)
[11:35:42]
[11:35:42] Received faulty work unit.
[11:35:52] logfile size: 20480
[11:35:52] - Writing 20992 bytes of core data to disk.
[11:35:52]
Originally posted by M
Originally posted by jaigandhi5+28 July 2004 - 16:43-->QUOTE (jaigandhi5 @ 28 July 2004 - 16:43)
Post Icons:
With an AMD processor, -forceSSE forces SSE on, -forceasm forces 3DNOW on and if you don't code either, you run with just normal processing. -forceSSE = fast, -forceasm = slower and no switch = very slow.
The -forceSSE switch forces an AMD processor to use its SSE optimizations. Use this switch only if SSE optimizations work well for you. If running the client under SSE optimizations causes too many problems, then switch to -forceasm, which will force 3DNow optimizations on an AMD processor. Seldom do AMDs have problems with 3DNow, but some do have trouble with SSE.
The assembly optimization for SSE is the code that occasionally pushes many AMD machines into unstable conditions. The parameter -forceSSE simply gives those who have demonstrated their machines are stable with SSE operations to regain the extra 15% speed boost that they had before the default was changed to 3DNow optimizations.
There are 3 types of code in the PC version of Gromacs: Unoptimized, 3DNow+, and SSE. How you invoke them was changed depending on the flags and the client version, but the fundamental code is still the same.
Originally posted by M