We host a php + firebird app for several years now, but as of late we are running into some scalability issues mainly with firebird as more and more new users are using the system.
The CPU usage is too high, but there's little query activity.
The queries/indexes are all performing very well, and we do heavy caching to minimize database accesses.
We are inclined to think the problem is in the connection creation/destruction overhead here.
We do not use persistent connections, and it may not be an ideal solution for us, there are some reports that firebird persistent connections on the PHP api are problematic.
I’ve been searching the web for the best practices and caveats I need to know to implement connection pooling for firebird, but have been coming up empty.
Can someone point me in the right direction here?
I found some software named "sql relay" but it looks abandoned. I'm having difficulty finding other options and tutorials.
The latest PHP 5.6 is running, as a fastcgi module under IIS 7.5 (win2008R2).
Our FB setup is 2.5, super classic.
We have 9 servers, 8 of them for the application and 1 for the database.
0 comments:
Post a Comment