By rlnorthcutt on

I am working on a site that is aggregating information from several sources and then using Services to make this available to other sites.

Some of the information we are aggregating contains 100-150 fields per record - so if I store these records as nodes, then I will have 100-150 CCK fields... which seems like alot. Especially as the number of records increases to 100k or more.

Is this too many fields? Should I break these records up into smaller nodes with references? Does it matter?

I will be caching much of the data, but I am still concerned about performance.

thoughts?

⋅ Categories: Drupal 6.x

Comments

lupo’s picture

lupo commented

I had a similar concern about a content type with many fields. Can anyone address this?

carwin’s picture

carwin commented

Have a lot of data being collectors for the users of a site, roughly 130 fields. Also using field_permissions to restrict access to various things by role.
This many fields with somewhere around 5 permission settings each freezes up Safari and crashes it. This also happened to me in Chrome but not in Firefox which makes me suspect Webkit has a problem with something.

Not sure if relevant, but at least somewhat related.