OS is Redhat 7.3. DB is MySQL because it has the fastest SELECT speed of any DB (so they say). Happy to use any DB - speed is the issue not rigid data integrity/rollbacks or finance per se. Berkeley won't work due to single reader/writer or multi reader config. Server has 2GB ram dual processors and all the RAID tweaks to minimize seek time. MySQL/OS compile tweaks to get around its ~800 query limit in stock form. Typical query is:
SELECT integer from client_X WHERE key IN ( ?,?,?,? ) ORDER BY key DES +C
Primary key is key. IN grouping 1 min, 10 max, average 3 typical 2-4.
Peak query rate can potentially exceed 10,000 per second. Base code all copes fine. DB not so happy at high loads.
cheers
tachyon
s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print
In reply to Re: Re: System V shared Memory Perl Module (more of a C question than Perl) aka Efficient SQL result caching
by tachyon
in thread System V shared Memory Perl Module (more of a C question than Perl) aka Efficient SQL result caching
by tachyon
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |