[erlang-questions] Building / releasing with HIPE / native
Wed Apr 2 20:27:58 CEST 2014
What does code:is_module_native(lists) say?
On 04/02/2014 08:11 PM, Adrian Roe wrote:
> We've been using Erlang in production for quite a few years now and for the first time we have a project that really benefits from HIPE / native code being turned on (before things have always been fast enough without and the benefit of more detailed stack traces etc outweighed any performance gains). We did some benchmarking by compiling single modules with HIPE - both in our application code and then going through key OTP / Erlang library modules, clearing sticky_directory errors and recompiling them one by one with +native.
> Now that it is clear that (for this use case) native / HIPE is the way to go, I went to the project's build box and recompiled Erlang (R16B03) from source with
> ./configure --enable-hipe --enable-native-libs
> in the expectation that all libraries would be compiled with +native
> Checking (for example) lists.beam gives:
>> Erlang R16B03 (erts-5.10.4) [source] [64-bit] [smp:8:8] [async-threads:10] [hipe] [kernel-poll:false]
>> Eshell V5.10.4 (abort with ^G)
>> 1> lists:module_info().
> No sign of native anywhere...
> I've tried this on OSX, CentOS and Ubuntu all with the same result, so it's clearly me doing something stupid, but I can't see it.
> I obviously could go through and rebuild each module in turn (as we did for the benchmarking) but it doesn't feel like the right way forward.
> Any suggestions gratefully received!
> Kind regards
> Dr Adrian Roe
> erlang-questions mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions