I think I should go toward cores over frequency, as MySql performs better in a multicore environment, so AMD should be the choice to go, as their 6-8 cores solutions are much more reasonably priced.
Anyhow an intel mobo + an intel cpu would be more stable, but more expensive
No, it won't be. Stability will be about the same. If you go with server parts, cheaper Opterons are pretty good values, but once you're into $200+ CPUs, Xeons start looking really good. For desktop components, the Intel 2500 and 2600 models are pretty much your only choices. Anything else will almost certainly have lower perf/$.
Cores v. frequency: they both matter. MySQL only prefers cores over speed for certain types of queries, so unless you've tested your software, don't assume that more cores is absolutely better. FI, just moving to a storage engine other than MyISAM will reduce the effectiveness of more cores on queries to those tables, all else being equal. Using transactions correctly all-around will also change performance in ways that definitely won't be benefited by more cores, but will really require testing to figure out. Also, having a well-normalized DB will generally make MySQL slower on simple queries (a well-normalized DB, properly using views, will handle heavy loads with varied queries better, but I doubt that's something you're going to care about).
Also, do you know much writing you will be doing, and of what sizes? If quite a bit of small writes, you may be more bottlenecked by a hard drive than by CPUs, in which case an SSD is in order, preferably an Intel 320 series, IMO (good RAID would cost too much). If it's mostly reading, you can just get gobs of RAM, and tune MySQL a bit for caches and buffers. OTOH, if you are writing or reading very large amounts, you may need a mechanical HDD for the capacity per dollar reasons.
And, doing scientific calculations, how do these scale out to threads, and what CPUs perform them best? This could very well have a greater impact than anything related to iBATIS and MySQL. I mean, if you are using iBATIS and MySQL just for a reliable data storage backend (the whole things looks like a waste of resources, to me, unless you're going to be using many computers, and when that happens, your current HW needs and assumptions will go out the window), they might have no more real performance impact than taking up some RAM, and adding write latencies.
Finally, how critical is it to
NEVER have a piece of corrupted data? What you get with Xeons and Opterons is the ability to have good ECC from end to end. Even Phenom IIs w/ Asus or Biostar mobos can't get you quite to level of an Opteron. If you just need 24/7 operation, any set of quality equipment will do. Bits flipping is typically pretty rare, but consumer hardware works on the assumption that it's rare enough not to matter. Server hardware goes by the assumption that a flipped bit going undetected will mean the end of the world. a Phenom II w/ the right mobo can get you in the middle, as well (also, if not buying for a month or two, maybe wait for BD, and see if it's any good, and if it is, if prices change).
Here's what I would do:
Spec out low-end Xeon and Opteron servers from HP and Dell (lately, I'm becoming fond of HP, again), and then some midrange/high-end
business desktops from them, as well. If your concern is stability, forget the penny-pinching typical consumer BS boxes. You can always make it yourself, but these should give you a good relative idea of what kind of performance you can get for what money, a bit quicker and easier (IE, how much cheaper can you build a desktop v. server, for your needs and budget). You can use these, and your actual reliability needs, to determine what kind of hardware to get. If you're definitely going to build, add 2-300 to the budget, when specing out the big vendor boxes.
Now, on a desktop system with decent specs, set up your software and do some performance testing (if you can't spare a whole system, use Virtualbox or VMWare on a PC
with HW virtualization support). Even very basic testing should be enough to figure out if you're more limited by CPU, RAM, disk, or even your code in general, and prioritize on that.