Even if you can do it (resource or data), this is a bad idea. You will have many simultaneous open connections that will explode your maximum connections very quickly ... especially if its life cycle extends beyond more than 100 ms (depending on your requests) to 20 minutes or more. With open connections, something like MySQL will also not be able to reset the memory allocation, and the whole system seems to be going to hell. In short, this is not what the database has if there is only one user in your code.
As an alternative, I highly recommend caching technologies that are designed specifically to reduce database load and reduce connection time. Using something like the simplest, memcached will significantly improve performance, and you can specify exactly how many system resources are in the cache, allowing the database to do its job of retrieving data when needed.
source share