pompomJuice uttered:
I suspected something like this, as it makes sense.
I have multiple binaries/different connections ( and I cannot make them
share a connection ) using this one lookup table and depending on which
connection checks first, it will update the table.
What is your working set like? Are all processes on the same machine?
Sounds like you might benefit from increasing the amount of RAM on this
machine. You may be thrashing the OS cache, as your lookup process hogs
memory for it's own cache, pushing out old pages from the OS filesystem
cache.
If RAM upgrade is not feasible, then try reducing the cache of the lookup
process, so that the OS cache isn't forced out of memory so easily. Then,
when the lookup process has a cache miss, it's missed page is more likely
to be in the OS memory cache, and copied to the lookup process at memory
copy speed.
As you may have guessed, choosing the correct cache size for the lookup
process may involve several tuning iterations.
Christian
--
/"\
\ / ASCII RIBBON CAMPAIGN - AGAINST HTML MAIL
X - AGAINST MS ATTACHMENTS
/ \
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
