in reply to Re^2: How best to optimize shared data
in thread How best to optimize shared data

Profiling lookups on one of our table using the existing code gives 670 lookups/second using the (poorly written, IMHO) database solution, versus 56,818/s for a direct perl hash lookup. This is a 100 fold improvement: and it's one that I can implement.

Well, we have indexes on all our key fields, and we don't do any writes.

Ok - you have indices, but are you using them? What is the execution plan for your queries? Why are you pulling all your data out instead of looking at it when you need it?

There are sooo many things involved in optimizing this kind of thing that you really need an expert on the ground, so to speak, to really give you more than just very generic places to look.

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

In Section Seekers of Perl Wisdom