Michael Steeves wrote: > * Doug Hughes ([email protected]) [100210 17:03]: > >> Your specs are pretty basic. You could get almost ANYTHING to fill these >> needs. You don't mention whether the app is CPU or memory bound, or if >> it would benefit from more throughput or less latency. These little >> details can make a difference, but you probably don't know at this point. >> > > > R is memory intensive. It's not multithreaded, so you typically don't > need the cores. We've got a system with 16 cores and 64G of RAM, and R > jobs will routinely eat up all 64G of memory, and leave 15 CPUs > sitting idle, at least on the Linux side of things. > > Whatever you get should have some space for memory expansion, even if > you start it out small. > > > > > -Mike > While R doesn't have threading support, it does have a package that provides MPI bindings that can make use of those extra CPUs. Obviously you need to have a problem that is parallelizable to take advantage of it.
-- -- Skylar Thompson ([email protected]) -- http://www.cs.earlham.edu/~skylar/
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
