When we are adding a text field to a content type the default length is 255. I am curious to know the performance effect of the field types and the length have for it.

Is there a preferred order of fields and length based on performance? so that we can chose our fields accordingly.

  • 1
    I'm no performance expert, but eh, I doubt it. It's more for how many letters/numbers/characters you want to allow for the field. For Example: 255 characters is overkill for a person's age or last name field. You don't want people putting funny long stuff there.
    – No Sssweat
    Oct 9, 2015 at 9:16
  • In my opinion the performance impace is minor vs. the maintainability of the field in case you chose length of 10 characters and one year later you'll want ir to change (you can't change the length after the field was created because it requires the DB table to change)
    – rreiss
    Oct 9, 2015 at 10:19

1 Answer 1


Going over 255 means that field can not easily be indexed and thus if you filter on it in views or in a query it will be slow. As long as you stay below this limit all is well.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.