And make 300,000 queries over TCP like getting the list of county names in a state, or getting the list of place names in a county, because my actual use case involves fuzzy matching an arbitrary subset determined by user input, of 18,000,000+ unsanitized data records against geographical place names so they can be assigned geometries?
I'd like the program to finish in 15 seconds or less, please.
If you're making 300K queries over TCP to a database in order to do a calculation, then I'd say you need a much better data structure and/or algorithm. Either that, or do the bulk of the calculations on the database in P/T-SQL, or pre-calculate before-hand so that your on-line queries are just lookups instead of actual calculations.
The train of the discussion, if you go and read the OP's link and inner links, is like this:
- Singletons are bad
- Why are singletons bad?
- They're not "real" OO, they're global state, they obfuscate dependency, etc, etc, etc
- But what if I just legitimately have a ton of global state?
- Use a database! Use a filesystem!
The last point in the chain admits that the first point is mistaken. "Use a database" is just saying "use someone else's code to solve your problem". What if the database is implemented using singletons? What if it uses code that isn't OO at all? All you've accomplished is to say "OO can't solve your problem, use something external". In fact, my problem is solved just fine by using a singleton.
I'd like the program to finish in 15 seconds or less, please.