So I don't think this is a mysql issue, but I wanted to bounce it off the
group anyways and see if anyone had seen similar behavior.
I'm running MySQL 4.1.10 on a Dell Poweredge 1850 with 2 EM64T Xeons and
2GB of memory running Redhat Enterprise 3 ES. I've been trying to address
some slowness in full-text searching a 120M table. So the first thing that
it occurs to me to do is expand the key_buffer_size to 1GB. At this size it
should be able to fully store the full-text index in memory. The only
problem is that MySQL doesn't seem to be growing, in memory, to the size
I've specified.
Doing a 'ps aux' reveals that MySQL is using 295MB of real memory and 1GB
of virtual memory - which makes me think I'm out of real memory. Performing
a 'Top' confirms that I have only 10MB of Real Memory available. However,
when I add up all the RSS values in the 'ps aux' it seems like I'm only
using about 350MB of memory. To further confirm I cat /proc/meminfo and get
this:
total: used: free: shared: buffers: cached:
Mem: 2073825280 2063302656 10522624 0 176189440 1421033472
Swap: 1875353600 401408 1874952192
MemTotal: 2025220 kB
MemFree: 10276 kB
MemShared: 0 kB
Buffers: 172060 kB
Cached: 1387508 kB
SwapCached: 220 kB
Active: 967092 kB
ActiveAnon: 362908 kB
ActiveCache: 604184 kB
Inact_dirty: 734648 kB
Inact_laundry: 173492 kB
Inact_clean: 47280 kB
Inact_target: 384500 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 2025220 kB
LowFree: 10276 kB
SwapTotal: 1831400 kB
SwapFree: 1831008 kB
HugePages_Total: 0
HugePages_Free: 0
Hugepagesize: 2048 kB
It seems like I have a very large value for Cached memory. Has anyone seen
this before? Can anyone explain it?
TIA for indulging me in a slightly off-topic question!
-Dan
