Alexander Moiseev

@seanshpark This tool already existed and was in active use in one of backends as a CLI utility. The effort here is to provide cross-backend variant of this utility which...

@seanshpark There's a memory measurement and allocation tracking utility which is currently used in private backend. This tool takes a CSV file with memory allocation info and creates SVG (using...

@seanshpark I'm not entirely sure which place is right for this utility, but I'm afraid there's will be a duplication of effort if this tool will be maintained separately both...

> So if you move the tool to ONE then user can use the tool with or without ONE-vscode. > Am I correct? That's right, the idea is to keep...

@hyunsik-yoon At first I though exactly of this approach :) In backend discussion it was stated that export of memory info outside of backend requires documented and extensible data format...

@seanshpark The problem with current implementation of `FixedArity` mixin is that it adds 'virtual' link to inheritance chain, which leads to various limitations related to runtime performance. The solution here...

> OK. So how's the performance gain? And what module for what model? Around 10-17% percent of compile time reduction for medium-sized models. I've shared some benchmarks in backend repository...

> Q) do you have any plans to revise codes in `compiler` modules too? I'm currently focused on backend optimization, but it can sure bring optimization to `compiler` modules too...