Measure IO time spend when running the unit tests

[lfdversluis]

To gain insight into the IO time consumed by tribler, I will profile the functions with yappi in databamanagers such as sqlitecacbedb to measure the time spent on IO time when running the unit tests.

Output:

Disk type	Runtime tests	IO Time
SSD
SATA

[lfdversluis]

Small update: ran the unit tests a while ago and measured the sqlitecachedb class of Tribler running the Tribler unit tests (so dispersy also runs but is not captured. The results indicated around 1-2% of the time was spend on IO, not significant at all thus.

Dispersy has a lot more IO and therefore impact. Running the Dispersy unit tests may give better insight, but won't simulate real behavior.

[lfdversluis]

Running only the dispersy unit tests and profile Dispersy shows similar results. Here is a screenshot when only filtering on database items:

The .incl is the percentage of time spent in that function, which amounts to ~4%. So the unit tests do not perform much database activity (as somewhat expected).
I think an idle run of tribler communities (allchannel, search etc.) provide better insight of actual behavior.

[ichorid]

RIP Dispersy