Help optimize D solution to phone encoding problem: extremely slow performace.

[Anonymouse]

On Saturday, 13 January 2024 at 12:55:27 UTC, Renato wrote:
> [...]
> Not a great profiling experience :). Anyone has a better 
> suggestion to "parse" the trace file?

As a drive-by suggestion and I hope it doesn't derail anything, 
but if you have the opportunity to run it on linux, have you 
tried profiling with callgrind instead, with {Q,K}Cachegrind to 
visualise things? Your repositories probably have them. 
(callgrind is a part of valgrind.)

The wiki only mentions callgrind in passing, but it has worked 
well for me. [(example)](https://i.imgur.com/WWZAwy3.png)