in-memory option
From: vsevolod afanassiev <vsevolod.afanassiev_at_gmail.com>
Date: Tue, 10 Jun 2014 22:15:46 -0700 (PDT)
Message-ID: <0e14a914-3194-435e-b185-b91f47eca3f1_at_googlegroups.com>
Not much new info in the presentation by Larry Ellison compared with the Open World presentation. It would be nice to know:
- how much the In-Memory Option will cost - I assume it will be separately licensed option like Partitioning
Date: Tue, 10 Jun 2014 22:15:46 -0700 (PDT)
Message-ID: <0e14a914-3194-435e-b185-b91f47eca3f1_at_googlegroups.com>
Not much new info in the presentation by Larry Ellison compared with the Open World presentation. It would be nice to know:
- how much the In-Memory Option will cost - I assume it will be separately licensed option like Partitioning
- how to estimate size of a table in compressed columnar format
- what happens if a table grows and no longer fits in memory?
- how long it takes to populate the in-memory columnar tables after database restart
- the columnar in-memory store - is it going to be re-sized by automatic shared memory management? or it will remain static?
- in all the 'real-life' examples - did they compare performance on the server with the same amount of memory? Or they added memory for the In-Memory Option?