Não foi possível enviar o arquivo. Será algum problema com as permissões?
Diferenças
Aqui você vê as diferenças entre duas revisões dessa página.
Ambos lados da revisão anterior Revisão anterior Próxima revisão | Revisão anterior Próxima revisão Ambos lados da revisão seguinte | ||
dicas:r-compila [2011/11/03 22:44] paulojus |
dicas:r-compila [2012/06/27 09:52] paulojus |
||
---|---|---|---|
Linha 43: | Linha 43: | ||
mesa-common-dev x11proto-core-dev x11proto-input-dev x11proto-kb-dev \ | mesa-common-dev x11proto-core-dev x11proto-input-dev x11proto-kb-dev \ | ||
x11proto-xext-dev xlibmesa-gl-dev xtrans-dev libtiff-opengl ivtools-dev tdl | x11proto-xext-dev xlibmesa-gl-dev xtrans-dev libtiff-opengl ivtools-dev tdl | ||
- | |||
</code> | </code> | ||
+ | |||
+ | == Sobre compilação e pacotes == | ||
+ | |||
+ | R-2.14.0 (and higher) comes with Luke Tierney's byte-compiler installed. Byte-compilation can speed up R computations by | ||
+ | a factor 5, although if your functions are just calls to compiled C code the speedup will be much | ||
+ | smaller. By default, only the required packages are byte-compiled. But if you set (in your bash profile) | ||
+ | |||
+ | export R_COMPILE_PKGS=1 | ||
+ | |||
+ | then all packages will byte-compile when installed. If you set | ||
+ | |||
+ | export R_ENABLE_JIT=3 | ||
+ | |||
+ | then all functions you define in your interactive or batch session will be byte-compiled the first time they | ||
+ | are entered into the workspace (and the same is true for all loops). \\ | ||
+ | It should be noted that some contributed packages have namespace problems when byte-compiled. | ||
+ | |||
+ | R-2.15.0 (i.e. R-devel) has parallel versions of Map() and mapply(). parallel makes fork or socket | ||
+ | cluster and has parallel random number generation. MPI clusters are handled (for now) by passing the | ||
+ | information to the snow package. | ||