Oh, and one other number - your original code with PGO on that same input - 72 ms. So, the double/triple table lookup/slice stuff is really all only costing around 72/66 =~ 9%.
- Unknown performance pitfall in tables? adnan
- Re: Unknown performance pitfall in tables? Stefan_Salewski
- Re: Unknown performance pitfall in tables? cblake
- Re: Unknown performance pitfall in tables? adnan
- Re: Unknown performance pitfall in tables... cblake
- Re: Unknown performance pitfall in t... cblake
- Re: Unknown performance pitfall ... adnan
- Re: Unknown performance pitf... cblake
- Re: Unknown performance pitf... cblake
- Re: Unknown performance pitf... cblake
- Re: Unknown performance pitf... cblake
- Re: Unknown performance pitf... cblake
- Re: Unknown performance pitf... cblake
- Re: Unknown performance pitf... cblake
- Re: Unknown performance pitf... adnan
- Re: Unknown performance pitf... cblake
- Re: Unknown performance pitf... cblake
- Re: Unknown performance pitf... cblake
- Re: Unknown performance pitf... mratsim
- Re: Unknown performance pitf... Araq