I've recently had to work on a code base that parses largish RDF XML files.
Part of the code base does relatively simple but regular expression
matches, but since the files are large, quite a lot of Regex.run calls.
While profiling I've noticed, that there are callouts to
:erlang.system_info, w
2024 at 4:37:43 PM UTC+1 José Valim wrote:
> I have pushed a fix to main. But also note we provide precompiled Elixir
> versions per OTP version. Using a matching version will always give you the
> best results and that's not only about regexes. :)
>
> On Thu, Mar 14,
provide precompiled Elixir
> versions per OTP version. Using a matching version will always give you the
> best results and that's not only about regexes. :)
>
> On Thu, Mar 14, 2024 at 2:20 PM Jan Krüger wrote:
>
>> I've recently had to work on a code base that pa
versions per OTP version. Using a matching version will always give you the
>>> best results and that's not only about regexes. :)
>>>
>>> On Thu, Mar 14, 2024 at 2:20 PM Jan Krüger wrote:
>>>
>>>> I've recently had to work on a code base
arking tool: comparing fprof results from different code may be
> misleading. Proper benchmarking is preferrable. I am benchmarking locally
> and I cannot measure any relevant difference even with the whole version
> checking removed.
>
> On Thu, Mar 14, 2024 at 6:01 PM Jan Krüger
t in pure running time of
>>>> the code, setting aside fprof. I'll post what I have after work today.
>>>>
>>>> On Thursday, March 14, 2024 at 10:21:25 PM UTC+1 José Valim wrote:
>>>>
>>>>> Do you have benchmarks or only the fprof result
you need to.
I am also not sure if fprof will consider the time spent on NIFs. I assume
most time is spent on the regex engine but if that is not fully considered
in fprof, that could affect measurements. But I am speculating here, I
truly don't know. :)
On Fri, Mar 15, 2024 at 8:31
