clock period, throughput and efficiency of I2C bus
There will not be an answer to get you specific throughput numbers without actually knowing what device protocol and operational procedure that you are using. Bus utilization efficiency goes up if you operate with transactions with the device that transfer more data per START / STOP sequence.

From a raw protocol perspective the I2C bus uses 8-bit data size with 9th bit acknowledge. So assuming an SCL clock generated at a uniform rate the raw transfer efficiency will be no better than 8/9 or about 88% efficiency.

To get an idea of how to address this lets take a specific example of a simple serial EEPROM that has an I2C interface and you want to read it two data bytes per transaction. There is some overhead that we could consider as follows:


Start sequence (lets guess at equivalent of 2 clock times).
Slave Address byte to set device select and upper address bits to read. (8 + 1 clocks).
Low address bits of where to read in EEPROM. (8 + 1 clocks)
Repeated Start condition to switch to read mode (guess at equivalent of 2 clock times).
Slave Address Repeat with Read bit set (8 + 1 clocks).
First byte read out (8 + 1 clocks).
Second byte read out (8 + 1 clocks).
Stop sequence (lets guess at equivalent of 2 clock times).
Null time between transactions (Lets guess at 5 clock times).


If you total up all the equivalent clock times above there are 56 of them with a usable 16 clocks of actual utilization to get the data that was being read. This gives a data access efficiency of 16/56 or about 28% efficiency.