Skip Navigation

[Closed] Importing a large set of data in WordPress using Toolset.

This support ticket is created 3 years, 9 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 1 reply, has 2 voices.

Last updated by Christian Cox 3 years, 9 months ago.

Assisted by: Christian Cox.

Author
Posts
#2025091

We are preparing a CSV for importing in WordPress using Toolset.
We will use WP all import plugin.
It includes a large set of properties (~ 1M).
We are wondering if the performance of WordPress will be affected after importing the data?
We have created multiple custom fields (custom post type = 'properties').
Could the import damage WordPress performance?
Should we consider any things to avoid degradation of the website?

#2025125

We are wondering if the performance of WordPress will be affected after importing the data?
I think yes, anytime you are working with a large database it will have some impact on the overall performance of the site. Queries will take longer because there is more data to consider. I've never personallly worked with a database containing a million posts, so I don't have a good frame of reference, so you might need to try it and see. You could try setting up a staging environment to perform the import before you import into the live site, for testing purposes.

We have created multiple custom fields (custom post type = 'properties').
Could the import damage WordPress performance?

Again, queries will take longer and will require more server resources. So yes, a large database size will make a noticeable impact on overall site performance. If you have custom search Views, those queries will take longer to perform and may require a large amount of server resources. More complex queries like distance-based searches will be impacted by a large database set, but that's just the nature of working with a considerable amount of data.

Should we consider any things to avoid degradation of the website?
You should consider optimizing your search queries for performance. Custom field queries, for example, are less performant than taxonomy queries (https://metabox.io/custom-fields-vs-custom-taxonomies/#:~:text=Because%20of%20the%20WordPress%20database,key%20and%20value%20is%20slow). You should consider using caching systems to help improve performance, CDNs for asset delivery, and robust server-side infrastructure. You might consider contacting your host company for more server-related optimization. I would also research WordPress optimization in general for large data sets, like limiting post revisions, managing expired transients, limiting comments, limiting pingbacks, etc.

The topic ‘[Closed] Importing a large set of data in WordPress using Toolset.’ is closed to new replies.