Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author htmlBurger

    (@htmlburger)

    Hi Alvaro,

    This is a good question – thanks!

    Basically, Carbon Fields uses the native WordPress APIs to retrieve and save data. Performance-wise, this makes it as efficient as WordPress itself is – no more, no less.

    However, usually for large projects, if you don’t plan your application architecture and data flow well, you can end up with large performance issues. Of course, any custom fields plugin (including Carbon Fields) will have several constraints if not used properly, for example: having 1000s of fields or 1000s of values on one page will cause performance issues, mainly with the browser rendering fields, but possibly also with the server when loading the values (if the server is slow).

    We’ve used Carbon Fields on many large projects without having any performance issues so far. So Carbon Fields is definitely a great solution for large websites. When planned well, a website built on top of it can be scaled to a very large one without having any performance issues.

    So, what are you waiting for, give it a try ??

    We’re glad to answer any other questions that you might have.

    Thread Starter Alvaro Gois dos Santos

    (@alvarogois)

    Thank you for your fast reply. I’ll give it a try.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Scaling and comparison with ACF and CMB2’ is closed to new replies.