Description of the need
Currently most tests are using the Standard profile. This causes lots of unnecessary overhead on each test because most tests only need a few modules installed.
Proposed solution
Change the default profile to one that has fewer tables to copy when setting up a new test prefix.
Additional information
This will probably break tests in contrib. This should be easy to mitigate by setting protected $profile = 'standard';
if you depend on something from the standard profile, but it will require changes from module maintainers.
Recent comments
This is helpful. When I Googled for suggestions about the error message, I found an old entry in Stack Overflow that suggested increasing max_connections. I passed that along to the hosting...
"SQLSTATE[08004] [1040] Too many connections" error - any ideas?
Thanks for the suggestions. All caches have been enabled from the start. I'm not sure what qualifies as a "complex" view. There are 400-500 pages that include EVA fields. But the vast...
"SQLSTATE[08004] [1040] Too many connections" error - any ideas?
Also, when we had some problems with the Backdrop sites, this is what the server admin did: I have increased the max_connections for mariadb and increased the child_processes for...
"SQLSTATE[08004] [1040] Too many connections" error - any ideas?