leomarquine / php-etl

Extract, Transform and Load data using PHP.
MIT License
178 stars 81 forks source link

Connection Cleanup #56

Open type1fool opened 3 years ago

type1fool commented 3 years ago

Problem

I have been using PHP ETL and the Parallel extension's functional API to ingest large CSV datasets. It has been reliable and fast, but there can be several hundred database connections left open until the ingest is complete. I poked around the source code for this ETL package, but there are no methods or documentation for removing connections.

For context, this is how the ingest script works:

Though I can't share any actual code, those closure bullet points are essentially what happens.

Inside the ETL closure, I have tried exit and return after $etl->run() completes, and I have tried unsetting the ETL instance in the closure. Still, the processes and DB connections remain open.

Documentation for the Parallel extension could be more robust.

Request

The Manager class would benefit from a removeConnection or destroyConnection method, where the conn would be removed from $connections. Would that terminate the PDO connection?

I'm happy to open a PR if this would work. I would also take advice on using persistent connections with ETL and Parallel.

ecourtial commented 2 years ago

Hi @type1fool I don't know if you are still interested by this feature, but we added it in our fork : https://github.com/wizaplace/php-etl

The implementation is very basic: it removes any reference to the connection, so the garbage collector could remove it on its next pass.

Official PHP Doc:

The connection remains active for the lifetime of that PDO object. To close the connection, you need to destroy the object by ensuring that all remaining references to it are deleted--you do this by assigning NULL to the variable that holds the object. If you don't do this explicitly, PHP will automatically close the connection when your script ends.

type1fool commented 2 years ago

Thank you, @ecourtial

I've changed jobs and I'm out of the PHP ecosystem now. Still, thanks for following up.