Best Materialized View configuration to achieve continuos huge load
I need to replicate rows from a range-partitioned (date) table T to a remote non-partitioned materialized view T' using all the fields of master table T.
All tests I did were wrong (on-demand fast refresh every 10,15, 20, 30 and 60 seconds) showing as if the fast refreshes overlap each other causing materialized view log to grow up faster than the mv T' is able to process.
Which is the recommend configuration to achieve a rate of 5000 transactions/second on mv T' (commit on every row in master table) ???
I heard about Partition Change Tracking (PCT) and atomic refresh and don't know if ithey can help me.