I believe the answer will be for you to create a single index on *just*
the cust column. (I assume that a specific cust id occurs only once or a
few times in the
whole table.) This will allow MySQL to use that index to find the small
set of records (quickly) where cust=1,
then to screen the email
> -Original Message-
> From: Dan Nelson [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 12, 2001 9:17 AM
> To: Joe Kaiping
> Cc: [EMAIL PROTECTED]
> Subject: Re: Can't get MySQL to use available memory (performance very
> slow)
>
>
> In the last ep
In the last episode (Sep 12), Joe Kaiping said:
> Hi there,
>
> I'm having trouble configuring MySQL 3.23.36 running on a Sparc/SunOS 5.8 to
> use the available 1 gig of memory and was wondering if anyone might be able
> to help find a solution.
>
> /usr/ucb/ps -aux gives the stats:
>
> USER
Hi there,
I'm having trouble configuring MySQL 3.23.36 running on a Sparc/SunOS 5.8 to
use the available 1 gig of memory and was wondering if anyone might be able
to help find a solution.
/usr/ucb/ps -aux gives the stats:
USER PID %CPU %MEM SZ RSS TT SSTART TIME COMMAND
root
