At 20:20 -0400 5/11/02, <sup-mysql@stripped> wrote:
>Paul,
> I dont quite understand what you mean when you say "I guess you
>want your machine to thrash, then."
Most people don't have over a gig of physical memory. Setting the buffer
sizes to such huge amounts in such cases will cause a lot of swapping,
completely obviating the attempt to improve performance.
>
>Ramon
>
>
>On Sat, 11 May 2002, Paul DuBois wrote:
>
>> At 15:44 -0400 5/11/02, <sup-mysql@stripped> wrote:
>> >Benjamin...
>> >
>> > I get a feel for the amount of activity by looking at the
>> >processes running and the amount of cpu time they are using.. (on
>> >linux: ps xu)
>> > Correct me if I am wrong. I understand that the sort_buffer is the
>> >most important when creating keys... I set the sort buffer to 1000M and
>> >key buffer to 200M.
>>
>> I guess you want your machine to thrash, then.
>>
>> How much physical memory do you actually have? 1200M?
>>
>> >
>> >Ramon
>> >
>> >On Sat, 11 May 2002, Benjamin Pflugmann wrote:
>> >
>> >> Hi.
>> >>
>> >> How do you define/determine "activity"?
>> >>
>> >> The operation is probably I/O bound. From the message you get I
> assume
>> >> increasing the key cache matter.
>> >>
>> >> Regards,
>> >>
>> >> Benjamin.
>> >>
>> >> On Sat, May 11, 2002 at 11:00:11AM -0400,
>>sup-mysql@stripped wrote:
>> >> > When loading large amounts of data into MySQL there is a
>>period oh high
>> >> > server activity followed by a long period of little
>>activity. While on the
>> >> > little activity period, the process list reads "Repair with
>>key cache"...
>> >> >
>> >> > How can I make the server work harder in this period and get done
> with
>> >> > loading data faster?
>> >> >
>> >> > Thanks
>> >> >
> > > > > Ramon
