JP Site Search - Recommended Typesense Server Setup
Article Index
- JP Site Search
- What is JP Site Search?
- What is Typesense?
- Typesense Hosting Options
- Recommended Typesense Server Setup
- Quick Docker Example
- Installation
- Initial Setup
- Sources and Providers
- Joomla Articles
- Joomla Contacts
- Joomla Categories
- DOCman Provider Add-on
- Indexing
- CLI and Cron
- Frontend Module
- Autocomplete Layouts
- Full Search Page
- Analytics and Search Quality
- Diagnostics
- Security Model
- Troubleshooting
- Recommended First Setup
- All Pages
Page 5 of 23
Recommended Typesense Server Setup
Typesense stores the search index in memory and keeps raw document data on disk. This means RAM, SSD storage, and stable CPU capacity are the most important server resources.
Small websites and development
- CPU: 1-2 vCPU
- RAM: 1-2 GB
- Disk: SSD storage
- Use case: development, small Joomla websites, proof of concept, low traffic
Normal production Joomla website
- CPU: 2-4 vCPU
- RAM: 2-4 GB or more depending on indexed content size
- Disk: SSD storage with room for raw document data and growth
- Use case: normal municipal website, company website, documentation website, intranet
Larger website or intranet
- CPU: 4+ vCPU
- RAM: sized according to indexed searchable data
- Disk: fast SSD/NVMe where possible
- Use case: large intranet, many articles/documents, many concurrent users, frequent indexing
For production systems where search uptime is critical, consider Typesense Cloud or a highly available Typesense cluster. A single self-hosted node is simpler, but it is also a single point of failure.
Always test with your real content size. Search performance depends on how many documents you index, how much text is searchable, how many fields are faceted, and how many users search at the same time.