Hi all,

This is semi-related to my other post: http://forums.asp.net/thread/1272346.aspx

So, if I are developing custom web parts, does anyone have a rule-of-thumb for how much data should be stored in a web part for editing. (Personalizable, WebBrowsable).  I am trying to leverage as much as I can from the default framework, but don't want to really bloat the personalization data.

I ask because I still have not found any performance documents, and I am implementing searching on all content.  So right now, I have all my parts implement an interface ISearchable, and when the part is saved I index all content int the part to a table with its location (page, zone, zone index), so i can create links to the content. (So I am pretty much storing all content twice, once as indexed readable text, and once as part of the personalization data serialized in its byte array format.)

Thsi was the only way I could think of to use the default personalization provider and make use of all the data stored as a byte array. 

Any thoughts/opinions? Thanks in advance.