#14 fpDb organization, possible room for performance improvemens
Closed: Fixed by polcak. Opened by polcak.

I noticed that the organization of fpDb is as follows:

list of wrappers (for each) list of tabIds (for each) object with internal data

Writing involves both wrapper name and tabId but reading is typically performed on tabId basis. Current structure requires that we iterate over all wrappers just to now if a hit was triggered in the tab.

It seems to me that a slight modification of the structure should provide benefits. I propose changing to:

list of tabIds (for each) list of wrappers (for each) object with internal data

This should be better for performance and also code readability.


Resolved in caa915d (devel0.7).

The correct ID is 527972b, merged in 6e04bbc.

Metadata Update from @polcak:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

Metadata