Thread

I have some questions on the performance implications of custom fields that don’t carry data. I’m experimenting with field groups and channel assignment, and am considering putting all custom fields in one large group, and using publish layouts to hide those that aren’t needed.

Are there performance hits for empty, assigned custom fields when the channel entries tag is used? Or otherwise?

Is there a performance or optimization reason to use field groups?

No, there shouldn’t be an impact. Unless you turn them off EE with the disable= parameter EE will get all your custom fields, whether you finally need them, or not.

So are you saying that the entries tag pulls all custom fields into memory, regardless of what custom field variables you indicate within the entries loop?

I’m curious if the ‘disable’ parameter stops the query into that portion of the database, but once it’s open, the extended performance hit is tied to what fields are called, or if it’s an all or nothing thing.

So are you saying that the entries tag pulls all custom fields into memory, regardless of what custom field variables you indicate within the entries loop?

Yes, because at that time it doesn’t know which ones you’re going to use.

I’m curious if the ‘disable’ parameter stops the query into that portion of the database

It does. If you are disabling custom fields they won’t be queried, meaning, yes, it’s all are nothing.