I have try to check the performances improvement that Hekaton engine brings converting a regular table to OLTP one. The regular table is 9 GB, but the Table Memory Optimization Adviser says it will need 553 218 MB RAM memory (that's half of TB ram). Is a such increase normal, or there something wrong with the adviser? If so, how can I calculated with T-SQL the amount of RAM memory needed?
The average metric is 3-5 times the amount of memory will be needed that the table actually occupies. It largely depends on how many versions of the rows will have to be maintained during your load processing. The majority of the performance enhancements you'll see will be if you can also use natively compiled procedures. If you're just using in-memory tables and mixing them with standard tables and standard procedures, you'll still see a performance benefit, but it might not be as radical as you expect.