<p>In sake of performance it would be better to create a custom field type and one or two record(s). </p>

<p>You can store your information/records in a separate table and link them with their ID to a category. Craft CMS will create a record in at least 4 tables for every elements and it has to join those tables to populate it. So an additional amount of 20k will decrease your performance for sure.</p>

<p>It's better to create a separate table rather than using categories for this task. You can combine your records with other elements with an normal Query like Craft does it with it's  ElementCriteriaModel.</p>

<p>It's going to be much more work if you are not used to Craft but it will help you in the future as a good practice </p>

CC BY-SA 3.0
2018-04-07T19:07:37.220Z
Thanks Robin that is a good idea.  So taking those records and putting them into a table outside of the normal Craft environment and using a Query to intersect the info with the native Craft environment like categories or entries?
Vin
CC BY-SA 3.0
2018-04-07T20:45:15.153Z
Yes - I wouldn't call if outside of Craft environment since it's the idea and philosophy behind Craft to customize things and enable you to do it... But yes
Robin Schambach
CC BY-SA 3.0
2018-04-07T21:14:02.880Z
Doing it that way would change things a bit but make the data more raw which would speed up the site in comparison to having it within categories or entires.  Thanks for helping me hash that out.
Vin
CC BY-SA 3.0
2018-04-07T15:04:57.007Z
2018-04-07T15:04:57.007Z
Robin Schambach
<p>What is the best way to handle 20,000 simple records?  The records need to be searchable and linked to categories.  What is the best way to handle so many records when each records or entry would be a simple phrase 5-10 words max.</p>

<p>I thought of categories but thinking 20k anything has to be thought out.  Since categories may or may not be most efficient, any ideas or way that you have done this in the past before with success?</p>

CC BY-SA 3.0
2018-04-07T11:00:20.740Z
Can you expand on what you mean by "handle 20,000 simple records"? Do you mean you have 20,000 entries that need to be organised into categories and be searchable? If that's the case then that's pretty much a case of creating 20,000 entries assigned to categories.
foamcow
CC BY-SA 3.0
2018-04-07T19:03:26.027Z
I have 20,000+ short phrase records.  To simplify it, the records are airplane parts.  There will be no other info but the fact of the name of the part.  So from what you are saying, entries and categories, there is no difference on performance?
Vin
<categories><database><records>
Best way to handle large amount of records
# Best way to handle large amount of records

(Asked by: username_0 on 2018-04-07)

What is the best way to handle 20,000 simple records? The records need to be searchable and linked to categories. What is the best way to handle so many records when each records or entry would be a simple phrase 5-10 words max.

I thought of categories but thinking 20k anything has to be thought out. Since categories may or may not be most efficient, any ideas or way that you have done this in the past before with success?

**Tags:** categories, database, records
> **Comments:**
> **username_1**: Can you expand on what you mean by "handle 20,000 simple records"? Do you mean you have 20,000 entries that need to be organised into categories and be searchable? If that's the case then that's pretty much a case of creating 20,000 entries assigned to categories.  
> **username_0**: I have 20,000+ short phrase records.  To simplify it, the records are airplane parts.  There will be no other info but the fact of the name of the part.  So from what you are saying, entries and categories, there is no difference on performance?  

---

## 1 answers

### Answer by username_2 on 2018-04-07. Score: 2 | Accepted answer

In sake of performance it would be better to create a custom field type and one or two record(s).

You can store your information/records in a separate table and link them with their ID to a category. Craft CMS will create a record in at least 4 tables for every elements and it has to join those tables to populate it. So an additional amount of 20k will decrease your performance for sure.

It's better to create a separate table rather than using categories for this task. You can combine your records with other elements with an normal Query like Craft does it with it's ElementCriteriaModel.

It's going to be much more work if you are not used to Craft but it will help you in the future as a good practice

> **Comments:**
> **username_0**: Thanks Robin that is a good idea.  So taking those records and putting them into a table outside of the normal Craft environment and using a Query to intersect the info with the native Craft environment like categories or entries?  
> **username_2**: Yes - I wouldn't call if outside of Craft environment since it's the idea and philosophy behind Craft to customize things and enable you to do it... But yes  
> **username_0**: Doing it that way would change things a bit but make the data more raw which would speed up the site in comparison to having it within categories or entires.  Thanks for helping me hash that out.  

---

