Scaling Issues with PHP/MySQL Search Engine - Seeking Advice

Hello fellow developers,

I'm reaching out for some advice on scaling my golf related niche search engine, which is built using PHP and MySQL. Initially, the setup worked beautifully, but as the database has grown to over 3 GB, I'm starting to experience performance issues.

The problem is that the database is not always responsive, especially when making more than 20 queries per minute. I've optimized my queries as much as possible, using indexes, caching, and efficient query structures, but the issues persist.

Here are some details about my current setup:

Server: Virtual Private Server (VPS) with 2 CPU cores, 4 GB RAM, and a 100 GB SSD
Database: MySQL 8.0 with InnoDB storage engine
PHP: Version 8.1 with APCu caching
Queries: Mostly SELECT statements with JOINs and ORDER BY clauses
I'm considering a few options to address the performance issues:

Upgrade server resources: Adding more CPU cores, RAM, and storage to the VPS might help improve database performance. However, I'm not sure if this will be enough to handle the growing database size and query load.

Switch to a different database: I've heard that databases like PostgreSQL, MongoDB, or Elasticsearch might be more suitable for large-scale search engines. However, I'm not sure if the benefits would outweigh the costs of migrating to a new database.

Optimize database schema: Perhaps there are ways to optimize the database schema to improve performance, such as partitioning tables, using full-text indexing, or implementing a message queue.

I'd love to hear from others who have experience with scaling search engines or large databases. What are your recommendations? Should I upgrade server resources, switch to a different database, or explore other optimization strategies?

Some specific questions I have:

What are the pros and cons of switching to a different database, such as PostgreSQL or MongoDB?

How can I determine if my database schema is optimized for performance?

Are there any caching strategies or query optimization techniques that I might be missing?

What are the best practices for scaling a search engine to handle a large volume of queries?

Thanks in advance for your advice and insights!

Best regards,

Mark Putter

Quote:

---

Originally Posted by Mark Putter

Hello fellow developers,

I'm reaching out for some advice on scaling my golf related niche search engine, which is built using PHP and MySQL. Initially, the setup worked beautifully, but as the database has grown to over 3 GB, I'm starting to experience performance issues.

The problem is that the database is not always responsive, especially when making more than 20 queries per minute. I've optimized my queries as much as possible, using indexes, caching, and efficient query structures, but the issues persist.

Here are some details about my current setup:

Server: Virtual Private Server (VPS) with 2 CPU cores, 4 GB RAM, and a 100 GB SSD
Database: MySQL 8.0 with InnoDB storage engine
PHP: Version 8.1 with APCu caching
Queries: Mostly SELECT statements with JOINs and ORDER BY clauses
I'm considering a few options to address the performance issues:

Upgrade server resources: Adding more CPU cores, RAM, and storage to the VPS might help improve database performance. However, I'm not sure if this will be enough to handle the growing database size and query load.

Switch to a different database: I've heard that databases like PostgreSQL, MongoDB, or Elasticsearch might be more suitable for large-scale search engines. However, I'm not sure if the benefits would outweigh the costs of migrating to a new database.

Optimize database schema: Perhaps there are ways to optimize the database schema to improve performance, such as partitioning tables, using full-text indexing, or implementing a message queue.

I'd love to hear from others who have experience with scaling search engines or large databases. What are your recommendations? Should I upgrade server resources, switch to a different database, or explore other optimization strategies?

Some specific questions I have:

What are the pros and cons of switching to a different database, such as PostgreSQL or MongoDB?

How can I determine if my database schema is optimized for performance?

Are there any caching strategies or query optimization techniques that I might be missing?

What are the best practices for scaling a search engine to handle a large volume of queries?

Thanks in advance for your advice and insights!

Best regards,

Mark Putter

---

Hi Mark Putter

I only know about the first issue, and my advice to you is to temporarily upgrade to 4?8 cores, 8?16 GB RAM if possible to see if the performance improves. This helps diagnose whether the bottleneck is due to resources.

Sharondam

Quote:

---

Originally Posted by Mark Putter

Hello fellow developers,

I'm reaching out for some advice on scaling my golf related niche search engine, which is built using PHP and MySQL. Initially, the setup worked beautifully, but as the database has grown to over 3 GB, I'm starting to experience performance issues.

The problem is that the database is not always responsive, especially when making more than 20 queries per minute. I've optimized my queries as much as possible, using indexes, caching, and efficient query structures, but the issues persist.

Here are some details about my current setup:

Server: Virtual Private Server (VPS) with 2 CPU cores, 4 GB RAM, and a 100 GB SSD
Database: MySQL 8.0 with InnoDB storage engine
PHP: Version 8.1 with APCu caching
Queries: Mostly SELECT statements with JOINs and ORDER BY clauses
I'm considering a few options to address the performance issues:

Upgrade server resources: Adding more CPU cores, RAM, and storage to the VPS might help improve database performance. However, I'm not sure if this will be enough to handle the growing database size and query load.

Switch to a different database: I've heard that databases like PostgreSQL, MongoDB, or Elasticsearch might be more suitable for large-scale search engines. However, I'm not sure if the benefits would outweigh the costs of migrating to a new database.

Optimize database schema: Perhaps there are ways to optimize the database schema to improve performance, such as partitioning tables, using full-text indexing, or implementing a message queue.

I'd love to hear from others who have experience with scaling search engines or large databases. What are your recommendations? Should I upgrade server resources, switch to a different database, or explore other optimization strategies?

Some specific questions I have:

What are the pros and cons of switching to a different database, such as PostgreSQL or MongoDB?

How can I determine if my database schema is optimized for performance?

Are there any caching strategies or query optimization techniques that I might be missing?

What are the best practices for scaling a search engine to handle a large volume of queries?

Thanks in advance for your advice and insights!

Best regards,

Mark Putter

---

Oh. As for the second problem, you should integrate Elasticsearch for the search part.



**Links removed by Site Administrator so it doesn't look like you're spamming us. Please don't post them again.**

Hi Mark,

You?ve already taken some smart steps with indexes and caching, so you?re on the right track. A 3GB DB isn?t huge by MySQL standards, so the bottlenecks are probably in query design, indexing strategy, or how results are being served rather than sheer database size. Let me tackle your questions point by point:

1. Upgrading Server Resources

Pros: Quickest short-term win. More RAM lets MySQL keep indexes and hot data in memory (InnoDB buffer pool size should be ~70?80% of your RAM). More CPU cores help with parallel queries.

Cons: If schema/query design is the bottleneck, throwing hardware at it will just delay the pain. Good as a short-term fix, but not the final solution.

2. Switching Databases

PostgreSQL: More advanced indexing options (GIN, GiST), built-in full-text search, and better query planner in many cases. Migration effort is non-trivial, but worth considering if you need richer search features.

MongoDB: Document-oriented, flexible schema. Good for hierarchical data, but less ideal for complex joins. Might not be a great fit if your dataset is highly relational.

Elasticsearch (or OpenSearch): Purpose-built for search. Extremely fast for full-text queries, scoring, and faceting. Common pattern: keep MySQL for transactional data, replicate searchable fields into Elasticsearch for querying.

👉 Many production ?search engines? actually use hybrid architecture: relational DB for storage + Elasticsearch for queries.

3. Schema Optimization

Audit indexes: EXPLAIN your queries to see if they?re hitting the right indexes. Composite indexes can often replace multiple single-column indexes.

Partitioning: Useful if you query only recent data or by category. But for 3GB, might be overkill unless tables are growing rapidly.

Full-Text Indexing: InnoDB supports full-text now; for keyword-driven search, this can outperform naive LIKE queries.

4. Caching & Query Optimization

Query Cache: MySQL dropped the built-in query cache, but APCu or Redis can cache hot queries at the application layer.

Result Caching: Cache common search results (e.g., ?golf courses in Florida?) in Redis with a TTL.

Pagination: For deep pagination, avoid OFFSET x LIMIT y (it scans a lot). Use keyset pagination (WHERE id > last_seen_id LIMIT n) for speed.

Denormalization: Sometimes it?s worth duplicating frequently joined data into a summary/search table.

5. Best Practices for Scaling Search Engines

Separate read vs write workloads (read replicas in MySQL).

Use a search-optimized system (Elasticsearch/OpenSearch) alongside your DB if searches are complex.

Monitor queries: Enable slow query log and analyze with pt-query-digest.

Optimize schema for read-heavy workloads (materialized views, precomputed tables).

My Recommendation for You Right Now

Check your slow queries with EXPLAIN and pt-query-digest.

Tune MySQL: Make sure innodb_buffer_pool_size is set to ~3GB (on your 4GB VPS).

Introduce Redis caching for repetitive searches.

If your search needs grow (faceted search, relevance ranking), pair MySQL with Elasticsearch instead of fully migrating.

So in short: tune what you have, add caching, then consider Elasticsearch if you need ?Google-like? search behavior. Switching wholesale to another DB won?t necessarily solve performance issues unless you pick one tailored to your use case.