I wouldn't move it unless you indeed have at least tens of thousands of records. You'll never see the performance difference for relatively small tables. (Reason: MySQL *tries* to keep as much data as it can in memory. When you use multiple databases, that means it has to allocate separate buffer areas for each database. Whereas when you use a single database, it can more efficiently keep reusing the single buffer area for that database. But I have, for example, a case where I *had* to use multiple databases [because they were created separately and are uploaded and updated by separate mechanisms]. And one of them has a single table with 14 million records. And yet even so my queries using the two databases are *reasonably* efficient. I'd probably gain maybe 25% performance if they were in one DB, but the effort to do that with all the other considerations just doesn't make it worth while.)
In other words: Don't sweat the small stuff until you find you really need to.
An optimist sees the glass as half full.
A pessimist sees the glass as half empty.
A realist drinks it no matter how much there is.