Hello all,
I’ve heard discussions in the past concerning tag pollution where too many tags might cause a performance hit. Does the same discussion apply to any custom field? I ask because, as my TW grows, I’m getting more custom fields. I woulnd’t say that I have a huge amount (currently there are 160 total fields in my TW, approximately half of which are custom).
What might be considered too many custom fields such that performance might be impacted? I’m asking that question because I’ve been considering converting a bunch of tiddlers that I use to store data in fields to dictionary tiddlers (my TW is basically being used as a database for Kansas railroads). This would reduce the number of total tiddlers I have as well as reducing the number of fields I have in use (not sure of the exact numbers). Part of me wants to do this an exercise and learning experience, but it would be a considerable amount of work as I have many filters that I use to present the data. I’d like to know if this might be worth the effort.
I don’t believe I have a big performance issue now that i fixed the issue I mentioned in Violations in console results - #17 by HistoryBuff. However, I would like to avoid one in the future.
Any comments / opinions are welcome.