>For exmaple, does the transaction throughput increase or decrease for having such concurrency control?
As increase or decreased as compared to what?
Not having "concurrency control"?
With Oracle readers do NOT block writers & writers do NOT block readers.
I have NEVER worried or thought about "concurreny control"; with the possible exception of SELECT .... FOR UPDATE.
>(1) Transaction scheduling
With Oracle transactions occur in the order they start processing data.
>(2) Timestamp Ordering
This may be important to some applications, but the underlying RDBMS does not care; at least not Oracle (see above)
>(3) Serialization Graph.
What is this & why would any RDMBS care about it?
I have to conclude you are coming to this forum with little or no knowledge of Oracle but know some other RDBMS where these issues had to be addressed.
Am I correct?
The short answer is IMO is that none of these impact transaction throughput in an Oracle database; unless poorly designed & implemented into the application.
You can lead some folks to knowledge, but you can not make them think.
The average person thinks he's above average!
For most folks, they don't know, what they don't know.
Good judgement comes from experience. Experience comes from bad judgement.