the reason for the high memory footprint was preloading M1 data, as opposed to loading H1 data by direct download. Since the M1 data is later internally converted to D1 anyway, it is indeed possible to largely reduce the memory allocation in this case. This will be implemented in the next beta version. Thank you for notifying us about this issue.