Message boards : BOINC client : What Instruction Sets does BOINC use?
Message board moderation
Author | Message |
---|---|
Send message Joined: 6 Oct 06 Posts: 8 |
Hi, I'm thinking about getting rid of my socket a mobo. Mainly because of these highly expensive / rare, power hungry cpus (No C'n'Q). Socket A cpus have the following instructions: MMX, 3Dnow (extended 3Dnow) and SSE Now i've chosen a socket 754 mobo. I guess i'll start with the fastest low budget sempron 3400+ (with C'n'Q, appr. 20W less than Socket A cpus). It supports MMX, 3DNow!, SSE, SSE2, SSE3 and AMD64 Will these additional Instruction sets be any advantage to the Socket A cpu? OR: What Instr. sets does BOINC use? OR: Do different projects use different instructions sets? Great if anybody could answer these questions! Thanx in advance, Steffen |
Send message Joined: 16 Apr 06 Posts: 386 |
Different projects use different instruction sets, since they all have different requirements. While things like SSE sound useful, for a number of projects they're inappropriate, whereas for others they may be very good. |
Send message Joined: 6 Oct 06 Posts: 8 |
Different projects use different instruction sets, since they all have different requirements. While things like SSE sound useful, for a number of projects they're inappropriate, whereas for others they may be very good. Thx! Now I would find it interesting what specific requirements different projects have. I mean every cheap video editing tool can tell me that. At least the programmers should know that and this information should be available. I think it could be quiet useful, for example if you have more than one computer like me (with different processors) to decide: What cpu is better for a specific project (or would it be a waste of (cpu-) time?) Greetings! |
Send message Joined: 16 Apr 06 Posts: 386 |
Honza has compiled a table of project performance versus architecture (Intel/AMD) which is quite useful for that purpuse, it's on our Synergy forums somewhere. |
Copyright © 2025 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.