Wat brengt de toekomst ons? Een snelle doorstoot naar naar een plek binnen de top 250 moet mogelijk zijn. Met meer trouwe foldinggebruikers kunnen we nog een pak hoger uitkomen. Ik wil dan ook alle nieuwe gebruikers welkom heten, want er zijn deze week toch weer een paar nieuwe aanmeldingen geweest.
Verder is het mogelijk om je client nog een beetje te tunen ->
Van Stanford:
I would appreciate it if anyone using these three techniques would please read this post. As you may or may not have realized, a number of members here have been complaining about work unit stability, specifically P3xx and P10xx series units. This small "mini-FAQ" intends to explain the effect of the three techniques above on stability, and what to do if you are having problems.
The first thing to remember is that "-forceasm" and overclocking both involve a tradeoff: you are trading the stability of the client for speed. The client's default settings and your machine's stock settings are both optimized for stability. When you apply "-forceasm" or OC your machine, you are giving up the stable defaults in favor of completing units "faster." The problem is that "faster" isn't always faster. Sometimes, the errors generated as a result of these methods will result in an overall speed loss: your machine is so unstable that it is unable to complete a significant fraction of its assigned work units. This is a bad thing for all involved. "-forceasm" forces on SIMD instructions that the client may have otherwise determined were unusuable due to stability problems. These instruction sets are usually faster, but if they don't work right, why use them?
"-advmethods" is different than either "-forceasm" or overclocking. "-advmethods" is a special client flag that signifies that you are willing to accept beta work units to be tested. Most of these work units have been stable, but lately people have been receiving units, using "-advmethods", that have not been processed properly. Most likely, this is the result of either of the two options described above. However, when using "-advmethods", you agree to accept beta test work units that may or may not be considered stable. In the past, units assigned under "-advmethods" have been the desirable Gromacs units, and this was the only way to get them. This is no longer true. Gromacs units are now distributed widely to clients not using any flags at all. In fact, I would expect to soon see a drop in the number of Gromacs core units on "-advmethods", as a new F@H core is released that will require beta testing. When, or if, this will happen is not known.
The end result of any of these three options is that you may be seeing stability problems where there have not been any in the past. P3xx and P10xx series work units seem to push machines much harder than other work units we have before. If you are seeing problems, the typical troubleshooting procedure we will ask you to follow where one or more of these options is used will look like this:
Reduce or remove any overclock that may be present. Overclocking your system beyond its rated specs always brings the possibility of large stability problems. Gromacs, in particular, has been known to highlight these problems. So, the first thing to do is reduce your OC.
Remove "-forceasm". If you remove this flag, you will be running with what the client considers the best SIMD instructions for your machine. You may incur a speed penalty, but which would you rather have: a working client, or a faster client that has errors on, in some cases, all of its work units, causing them never to be credited?
Remove "-advmethods". Using "-advmethods", as mentioned, means you agree to accept work units that are in the late beta stages of testing. They cannot be guaranteed stable; by definition, they are still under testing. If you cannot process "-advmethods" units, please do everyone involved a favor and remove the flag.
If you are still experiencing issues after going through the above list, please post a topic here. We will do our best to help you sort out any problems.
P4:
forcesse & -forceasm = precies hetzelfde
AMD:
forcesse = SSE gebruik forceren
forceasm = 3dnow gebruik forceren
En verder:
We have been working with the Gromacs developers, AMD, and several mods to fix the AMD freeze issue discussed in the "Freezing with AMD and SSE - Discussion" thread in this section. In internal and beta testing, a newly prepared core has seemed successful thus far. For those who are interested in trying it immediately, we have made the new core available for manual download at http://www.folding.org/beta-core (instructions are listed there as well). Please note that you do not need to download now if you do not want -- if this core continues to look good, clients will soon automatically upgrade to it.
Some release notes:
- It is very slightly faster than the old core
- No bugs have been found in Gromacs, but this includes a workaround which seems to solve the problem
- The FAH team and the AMD team are cooperating fully to reach a final solution
If you check out the new core, please report any problems here.
), transporteer ik alles via een memorystick. Uploaden doe ik bij mij thuis.
).
