PHPackages                             eliasfernandez/phphinder-bundle - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. eliasfernandez/phphinder-bundle

ActiveLibrary[Utility & Helpers](/categories/utility)

eliasfernandez/phphinder-bundle
===============================

Bundle to connect PHPhinder with Symfony

v0.1.11(1y ago)567mitPHP

Since Dec 28Pushed 1y ago1 watchersCompare

[ Source](https://github.com/eliasfernandez/phphinder-bundle)[ Packagist](https://packagist.org/packages/eliasfernandez/phphinder-bundle)[ RSS](/packages/eliasfernandez-phphinder-bundle/feed)WikiDiscussions main Synced 1mo ago

READMEChangelogDependencies (4)Versions (20)Used By (0)

PHPhinder Bundle
================

[](#phphinder-bundle)

[![License](https://camo.githubusercontent.com/8bb50fd2278f18fc326bf71f6e88ca8f884f72f179d3e555e20ed30157190d0d/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f6c6963656e73652d4d49542d677265656e2e737667)](LICENSE)
[![Packagist](https://camo.githubusercontent.com/491c26f390dd953b6b1e150d3e1183fdb3eea408af338a41ee9af4782e2c21bc/68747470733a2f2f696d672e736869656c64732e696f2f7061636b61676973742f762f656c6961736665726e616e64657a2f70687068696e6465722d62756e646c652e737667)](https://packagist.org/packages/eliasfernandez/phphinder-bundle)

---

What is it?
-----------

[](#what-is-it)

[PHPhinder](https://github.com/eliasfernandez/phphinder) is an open-source, lightweight, and modular search engine designed for PHP applications. It provides powerful search capabilities with a focus on simplicity, speed, and extensibility.

The PHPhinder bundle connects PHPhinder with Symfony to improve the searchability of Doctrine entities.

---

Installation
------------

[](#installation)

Install PHPhinder via Composer:

```
composer require eliasfernandez/phphinder-bundle
```

---

Usage
-----

[](#usage)

### Entities

[](#entities)

Imagine a book entity we want to optimize to search for. This is how it could look like:

```
class Book
{
    #[ORM\Id]
    #[ORM\GeneratedValue]
    #[ORM\Column]
    #[PHPhinder\Property(Schema::IS_UNIQUE | Schema::IS_INDEXED | Schema::IS_REQUIRED| Schema::IS_STORED)]
    private ?int $id = null;

    #[ORM\Column(length: 255)]
    #[PHPhinder\Property(Schema::IS_INDEXED | Schema::IS_STORED | Schema::IS_REQUIRED | Schema::IS_FULLTEXT)]
    private ?string $title = null;

    #[ORM\Column(type: Types::SIMPLE_ARRAY)]
    private array $authors = [];

    #[ORM\Column(type: Types::TEXT)]
    #[PHPhinder\Property(Schema::IS_INDEXED)]
    private ?string $description = null;
...

    #[PHPhinder\Property(Schema::IS_INDEXED | Schema::IS_REQUIRED, name: 'authors')]
    public function getAuthorsCsv(): string
    {
        return implode(', ', $this->authors);
    }}
```

### Controller

[](#controller)

On the controller side we'll need to configure the Search engine to look for `Book` objects:

```
    private SearchEngine $searchEngine;

    public function __construct(private StorageFactory $storageFactory, private SchemaGenerator $schemaGenerator)
    {
        $this->searchEngine = new SearchEngine(
            $this->storageFactory->createStorage(
                $this->schemaGenerator->generate(Book::class)
            )
        );
    }
```

Then, in the actions, we can get results with one single method:

```
    #[Route('/search', name: 'app_search', methods: ['GET', 'POST'])]
    public function index(Request $request): Response
    {
        $query = $request->query->get('q', '');
        $results = [];

        if ($query) {
            $results = $this->searchEngine->search($query);
        }

        return $this->render('search/index.html.twig', [
            'query' => $query,
            'results' => $results,
        ]);
    }
```

### Configuration

[](#configuration)

#### `phphinder.storage` and `phphinder.name`

[](#phphinderstorage-and-phphindername)

You can define where the indexes are going to exist by configuring these two variables:

- phphinder.storage could be `dbal`(search entities will live in a database), `redis` (entities stored in a redis engine) or `json` (in this case the data is stored in files).
- phphinder.name depending on the chosen storage the name will be considered as a folder inside the `var` folder on the project (in case the storage is json) or as database defined by a DBAL dsn connection string.

#### `phphinder.auto_sync`

[](#phphinderauto_sync)

If `auto_sync` is enabled. Every time a searchable entity is added or updated the search engine will store the neccesary indexes. Attention: It could have a very high impact in systems with a high volume of writing in the database.

### `phphinder.sync_in_background`

[](#phphindersync_in_background)

When `sync_in_background` is enabled, a message is sent to the queue, and the message handler triggers an event to index the entity in the search engine. This process is nearly immediate, enabling the loading of 100,000 records in approximately 2 minutes. The actual message consumption process takes longer but does not impact entity generation. This can be done in parallel by as many consumers as needed.

---

### Performance

[](#performance)

As with any search engine, index creation is significantly slower than generating entities in the database. Indexing involves splitting documents into tokens, transforming these tokens into relevant search strings, aggregating a fuzzy search state index, and (the most time-consuming part) persisting these calculations to storage.

By default, this bundle triggers the indexing mechanism on entity persistence. While convenient, this approach can noticeably affect overall application performance. To mitigate this, indexing logic can be moved to queue processing using the `sync_in_background` parameter.

Performance also varies based on the storage backend. Let’s evaluate some configurations. Using the [phphinder-project](https://github.com/eliasfernandez/phphinder-project), we measure the time required to create the first 3,000 books and then test search performance for the common keyword `human`. These metrics provide insights into indexing and search speed.

---

### Hardware Specifications

[](#hardware-specifications)

- **Processor:** AMD Ryzen 7 5700G with Radeon Graphics (16 cores)
- **Memory:** 32GB RAM

---

### `auto_sync` with JSON Storage

[](#auto_sync-with-json-storage)

#### Indexing Speed

[](#indexing-speed)

 ```
xychart-beta
    title "JSON"
    x-axis "Books Inserted" 100 --> 3000
    y-axis "Time in ms" 500 --> 300000
    line [1485, 2067, 3457, 5188, 8956, 8915, 13680, 13053, 18001, 16520, 24276, 28433, 33869, 39637, 51672, 59923, 62133, 62179, 65565, 61010, 107375, 86390, 67906, 108845, 99148, 131471, 121568, 120736, 256062, 172580]
```

      Loading **Conclusion:** Very slow.

It is fast for the first entities but starts to degrade with linear growth. The larger the files, the longer it takes to write to them.

---

#### Search Speed

[](#search-speed)

**Conclusion:** Very fast.

It takes only 106ms to load `human` search results.

---

### `auto_sync` with DBAL (PostgreSQL)

[](#auto_sync-with-dbal-postgresql)

#### Indexing Speed

[](#indexing-speed-1)

 ```
xychart-beta
    title "DBAL (PostgreSQL)"
    x-axis "Books Inserted" 100 --> 3000
    y-axis "Time in ms" 500 --> 10000
    line [6844, 5716, 6487, 6955, 8665, 7076, 8576, 7154, 7558, 6448, 7790, 7617, 7835, 7921, 8936, 9055, 8858, 7971, 7661, 6206, 8343, 7033, 6102, 7190, 6491, 7886, 7578, 7092, 8666, 5999]
```

      Loading **Conclusion:** Slow but does not degrade.

It takes an average of 7.5 seconds to process 100 entities and maintains this performance regardless of the number of entities.

---

#### Search Speed

[](#search-speed-1)

**Conclusion:** Very fast.

It takes 106ms to load `human` search results, similar to JSON storage.

---

### `auto_sync` with Redis Storage

[](#auto_sync-with-redis-storage)

#### Indexing Speed

[](#indexing-speed-2)

 ```
xychart-beta
    title "Redis"
    x-axis "Books Inserted" 100 --> 3000
    y-axis "Time in ms" 500 --> 2500
    line [1117, 1000, 1115, 1273, 2377, 1331, 1616, 1373, 1483, 1293, 1543, 1520, 1621, 1630, 1821, 1863, 1808, 1690, 1679, 1399, 1808, 1590, 1402, 1583, 1484, 1755, 1694, 1698, 1948, 1494]
```

      Loading **Conclusion:** Fastest option.

It averages 1.5 seconds to process 100 entities and maintains this speed regardless of the total number of entities.

---

#### Search Speed

[](#search-speed-2)

**Conclusion:** Slow.

It takes 700ms to load `human` search results. This could be related to the implementation of the Redis storage or limitations with Redis itself. Performance remains consistent even with 100,000 books.

---

### Final Notes

[](#final-notes)

 ```
xychart-beta
    title "In Comparison"
    x-axis "Books Inserted" 100 --> 3000
    y-axis "Time in ms" 500 --> 300000
    line [1485, 2067, 3457, 5188, 8956, 8915, 13680, 13053, 18001, 16520, 24276, 28433, 33869, 39637, 51672, 59923, 62133, 62179, 65565, 61010, 107375, 86390, 67906, 108845, 99148, 131471, 121568, 120736, 256062, 172580]
    line [6844, 5716, 6487, 6955, 8665, 7076, 8576, 7154, 7558, 6448, 7790, 7617, 7835, 7921, 8936, 9055, 8858, 7971, 7661, 6206, 8343, 7033, 6102, 7190, 6491, 7886, 7578, 7092, 8666, 5999]
    line [1117, 1000, 1115, 1273, 2377, 1331, 1616, 1373, 1483, 1293, 1543, 1520, 1621, 1630, 1821, 1863, 1808, 1690, 1679, 1399, 1808, 1590, 1402, 1583, 1484, 1755, 1694, 1698, 1948, 1494]
```

      Loading Looking at the results, JSON is not recommended as a storage option except in specific cases:

- Fewer than 5,000 documents need indexing.
- The application is static and infrequently updated.
- Database usage is restricted or costly.

For write-intensive applications where search speed is less critical, Redis is the best choice. However, for most use cases, DBAL provides a good balance of indexing speed, search performance, and reliability. With `sync_in_background`, DBAL is fast enough for indexing, very fast for searches, and highly reliable.

Try it out with the [PHPhinder project](https://github.com/eliasfernandez/phphinder-project)!

###  Health Score

28

—

LowBetter than 54% of packages

Maintenance46

Moderate activity, may be stable

Popularity13

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity37

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~5 days

Recently: every ~15 days

Total

17

Last Release

414d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/a25d7763a37c3b0f6f11de3faf29fce6c03ebb0338c5347166ed475a1b4e19b8?d=identicon)[eliasfernandez](/maintainers/eliasfernandez)

---

Top Contributors

[![eliasfernandez](https://avatars.githubusercontent.com/u/1588390?v=4)](https://github.com/eliasfernandez "eliasfernandez (19 commits)")

### Embed Badge

![Health badge](/badges/eliasfernandez-phphinder-bundle/health.svg)

```
[![Health](https://phpackages.com/badges/eliasfernandez-phphinder-bundle/health.svg)](https://phpackages.com/packages/eliasfernandez-phphinder-bundle)
```

###  Alternatives

[sylius/sylius

E-Commerce platform for PHP, based on Symfony framework.

8.4k5.6M648](/packages/sylius-sylius)[sulu/sulu

Core framework that implements the functionality of the Sulu content management system

1.3k1.3M152](/packages/sulu-sulu)[prestashop/prestashop

PrestaShop is an Open Source e-commerce platform, committed to providing the best shopping cart experience for both merchants and customers.

9.0k15.4k](/packages/prestashop-prestashop)[contao/core-bundle

Contao Open Source CMS

1231.6M2.3k](/packages/contao-core-bundle)[leapt/core-bundle

Symfony LeaptCoreBundle

2529.1k4](/packages/leapt-core-bundle)[open-dxp/opendxp

Content & Product Management Framework (CMS/PIM)

7310.3k29](/packages/open-dxp-opendxp)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)