Trying to determine memory requirements can often be one of the hardest problems for Oracle connector users, particularly when they are unaware of their transaction volume or patterns.

While the current JMX metrics do provide information about the number of active transactions, we do not provide any further detail about what makes up those transactions, such as how many events are buffered or how many events are buffered per transaction.

We should look at seeing whether or not any of these metrics make sense and if so, how we could provide these in an efficient way that would work across all cache implementations without any or with minimal IO overhead.